GDDM V3R2 Diagnosis
|
Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF |
BOOK
Action functions GDDM V3R2 Diagnosis SC33-0870-01 |
|||||||||
The action functions that you can specify are summarized in this table: Function Arguments ABEND (number) CDPDS [({ON|OFF|control})] CGMREP [({ON|OFF|control})] DSOPEN [({ON|OFF|control})] FLOW none FREGS none FULLIO [({ON|OFF|control})] FULLTCA [({ON|OFF|control})] GREGS none HRIG [({ON|OFF|control})] LIST (low_address[, length]) NULL none PARMSF [(number)] PARTIO [({ON|OFF|control})] POSTSCR [({ON|OFF|control})] PRINT ("control_string" [, remaining_parameters]) STGREP [({ON|OFF|control})] TIME none TRACE (number,ON|OFF) 5080IO [({ON|OFF|control }[, number])] All the actions for which you can specify a control parameter are latched, that is, the action is inactive until you specify it to be ON. It then remains ON until you specify it to be OFF. Details of the control parameter are given on topic 2.7.5. The order in which the actions take effect (that is, place information in the trace output file) is fixed to minimize duplication. For example, if two separate conditions are satisfied, both of which call for a time stamp, only one time stamp is placed in the trace file. The order in which the actions are evaluated is:
A detailed description of each action function is given below, in alphabetic order. Subtopics: |
Copyright IBM Corporation 1990, 2012 |