

Log Function › Initiate Logging at CICS Startup
Initiate Logging at CICS Startup
You may want to begin logging as soon as CICS starts up. One way to do this is for an operator to initiate logging, but it's possible that some transactions may be entered before logging is initiated.
Follow these steps:
- Log a test stream with the following name:
- DDname
-
Default
- Application
-
CLIST
- Member
-
Meaningful name; for example, LOGSTART
- Version
-
Default
- Include the following in the test stream:
- Enter the following:
XTCA L.M.
- Complete the Multiple Terminal Log menu, naming the test stream to be logged; for example, GENERAL.NETLOG.001.
- Press Enter to initiate logging.
- Terminate the log of CLIST.LOGSTART.
Now you have a test stream which will initiate logging whenever it is run.
- Next, add a card reader/line printer to your TCT which contains:
XTCA EXEC LOGSTART
This automatically initiates test stream LOGSTART whenever CICS starts up.
- If you intend to use LOGSTART at each CICS startup, include screens in the beginning to delete or rename the NETLOG test stream from the prior CICS run. Otherwise, LOGSTART will get a Name in Use message when it tries to start the log.
- Alternately, you can edit the LOGSTART test stream and change the version number to activate logging during the next CICS startup. Leaving the version the same can be used to prevent activation. In other words, change the version only when you want to activate logging.
See Command List Processor in the "Run Function" chapter for more information.
Copyright © 2012 CA.
All rights reserved.
 
|
|