KB Article #177544
How to get notified on a TSO/ISPF session about a CFT transfer request
Problem
How to get notified on a TSO/ISPF session about a CFT transfer request
Getting transfer result details directly on a TSO session using the NOTIFY feature
Resolution
To get notified directly of all messages related to a transfer request, you can add the NOTIFY parameter to the CFT SEND or RECV command.
When set with your TSO UserID, all transfer related messages will be notified to your session.
It ease to follow interactively the transfer without having to access the Transfer CFT log or catalog.
Note:
- The APF is mandatory.
- The related CFTSEND or CFTRECV macro MUST be set with OPERMSG=255
- It can also be added to the default CFTSEND and CFTRECV
Notification can also be directed to a console, please, see the User Guide documentation for more details about the Transfer CFT NOTIFY feature
Warning*: Depends of the SGINSTAL options retained for the WTO descriptor and routcode, and in regards of the CFTLOG OPERMSG value, notifying a console may ends with transfer's messages printed twice!
Examples:
A) CFTSEND defined as below:
CFTSEND ID = MyIDF,
NOTIFY = &USERID,
OPERMSG = 255,
...
1) Send transfer related log messages as notifications to the UserID owner of the transfer request
Command example: SEND PART=MyPart,IDF=MyIDF, FNAME=MyFile
2) Send transfer related log messages as notifications to another UserID
Command example: SEND PART=MyPart,IDF=MyIDF, FNAME=MyFile, NOTIFY=MyFriendUserID
3) Send transfer related log messages to the console
Command example: SEND PART=MyPart,IDF=MyIDF, FNAME=MyFile, NOTIFY=OP
Warning: messages can be printed twice*
B) CFTSEND defined as below:
CFTSEND ID = MyIDF,
OPERMSG = 255,
...
Notifying the UserID owner of the transfer request:
Command example: SEND PART=MyPart,IDF=MyIDF, FNAME=MyFile, NOTIFY=&USERID
In that case, without a NOTIFY at command level, messages are printed into the console