Although DIS-D is meant for internal use and is, therefore, not documented, the user reporting the problem might be asked by ROSCOE Support to issue the DIS-D diagnostic DISplay monitor command, save the output and then send it to Support.
- Step 1. <SET COPYDEST ROS1> to alter default if necessary
- Step 2. DIS-D
- Step 3. (enter problem subcommand at the ENTER COMMAND prompt)
- Step 4. :C (hit PF12) ? this copies the screen to the AWS
- Step 5. PF8 ? goes to next screen
- Step 6. Repeat step 5 and 6 until the entire display has been copied
- Step 7. END (to end the DIS monitor at the ENTER COMMAND prompt)
- Step 8. A (attach the AWS)
- Step 9. If possible, edit out the command lines from each screen copied
- Step 10. PRINT AWS xxx, or save it to ROSLIB member or EXPort it to PS data set or PDS data set member
- Step 11. Fax, FTP or mail the output to CA technical support
- Step 1. DIS-D AWS (to route output from subsequent subcommands to active AWS)
- Step 2. (enter problem subcommand at the ENTER COMMAND prompt) Please note, you don't see any result as it is written to AWS
- Step 3. END (to end the DIS monitor at ENTER COMMAND prompt)
- Step 4. A (attach the AWS)
- Step 5. PRINT AWS xxx, or save it to ROSLIB member, or EXPort it to PS data set or PDS data set member
- S tep 6. FAX, FTP or mail the output to CA technical support
Other Relevent Information:
The first method should be used when the resulting output from the DIS-D command exceeds your AWS line limit. So you can save the (edited) screen data using IMPort into a sequential file with specifying DISP MOD on the second and any subsequent IMPort command.
In case the resulting output does not exceed your AWS line limit the second method may be recommended as there is no need to edit the resulting AWS to remove the command and header lines from each copied screen.