Terminal session journal log and screen-print data set
The terminal session journal log is a local journal (BBIJRNLL) allocated in each UAS that can be used to record all user commands and system responses.
Terminal session screen images can be captured by using the PRINT (PF4/16) key and are recorded in a BBISPRNT data set. BBIJRNLL and BBISPRNT are allocated with the MainView CLIST, as described below.
Allocating the terminal session journal or screen-print data set
A local journal log for user commands and system responses (BBIJRNLL) and a screen print log (BBISPRNT) can be allocated to a UAS.The terminal session journal (BBIJRNLL) and screen print data set (BBISPRNT) are allocated by the following MainView CLIST parameters:
JOURNAL (YES)
PRINT(YES)
The contents of the BBISPRNT data set can be printed later (see the sample JCL in BBSAMP member SLOGJCL).
The terminal session journal log wraps around when full. The log reinitializes and recording starts at the beginning of the data set. All information previously recorded on the data set is lost.
When a journal log restarts after the terminal session stops for any reason, log recording resumes where it was before the terminal session stopped.
Viewing a terminal session journal log online
Use the Log Display option from the Primary Option Menu to view a terminal session journal log online. The log displayed is identified by the entry in the TGT field, which can be changed. Enter LOCAL in the TGT field to display the terminal session journal log.
Printing a terminal session journal log
- Copy the sample procedure in BBSAMP member DLOGJCL.
- Edit the copy that you created:
- Replace the PROC statement with a JOB statement.
- Change the BBIJRNL data set names to reference the terminal session journal log data set.
- Submit the job.
Related topic