|
|
|
When problems do occur, it is not always possible to notify users that their file transmissions have failed. To determine the cause of the problem, you can log onto the source region and determine the cause of the transmission failure through standard panels. When the error is isolated, the request can be restarted if possible, or deleted and a new request issued. Remember that for staged transmissions, this may result in data sets not being deleted.
NCL procedures, executed after a successful file transmission, write messages to the activity log. This is a useful source of information.
More complete notification techniques, following successful or unsuccessful file transmissions, can be implemented by trapping the relevant messages (both standard messages and the messages issued by the NCL procedures executed at successful completion of the transmission) in an activity log exit procedure.
An installation can implement new NMCMD subcommands that let users track transmission requests and delete unwanted requests and data sets.
| Copyright © 2010 CA. All rights reserved. |
|