Generate and retrieve CA 2E joblog

Products

• CA 2E

Issue/Introduction

The joblog is the main source for troubleshooting CA 2E related issues and this article provides steps in details how the joblog can be generated and retrieved.

Environment

CA 2E 8.7 and higher

Resolution

Follow these steps

1) CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES)  

   Note: Consult your system admin if you have issue running this command. For example, you may need to login as  QSECOFR.  

2) Replicate the issue

3) Create a temporary file to store the log inforamtion by below command
"CRTPF FILE(QGPL/MYDATA) RCDLEN(133) MBR(*NONE) MAXMBRS(*NOMAX)"

3) Print the joblog by "DSPJOBLOG OUTPUT(*PRINT)"  

4) Find the latest spool file "QPJOBLOG" by using the "WRKSPLF" command.

5) Note down the spool number by taking F11 on the WRKSPLF screen untill we get the Spool File Nbr . 

6) copy the spool file to file QGPL/MYDATA which was created in the 3rd step by below command.
"CPYSPLF FILE(QPJOBLOG) TOFILE(QGPL/MYDATA) JOB(*) SPLNBR(3) TOMBR(XYZ)"

Note: Give correct spool file number which we note down from the last step 5.

7) FTP the QGPL/MYDATA to windows and send to Broadcom Support case for further analysis.

Open the command line in windows and execute the below commands to "FTP the QGPL/MYDATA to windows"
a) FTP <ibm-i>
b) <user-profile>
c) <password>
d) LCD C:\Temp  (If temp folder is not present create temp folder in C:\ drive)
e) CD QGPL
f) QUOTE SITE NAMEFMT 1
g) GET MYDATA.FILE/MYDATA.MBR
h) QUIT

Additional Information

Regarding log level in step 1 :

Please use log level 4 as indicated unless instructed by Broadcom Support.

All possible log levels:

0
No data is logged.
1
The only information to be logged is all messages sent to the job's external message queue with a severity greater than or equal to the message severity specified. Messages of this type indicate when the job started, when it ended, and its status at completion.
2
Level 1 logging information and any requests that result in high-level messages with a severity greater than or equal to the severity specified. If the request is logged, all of its associated messages are also logged.
3
All requests and commands run by a CL program if allowed by the Log CL program commands job attribute and the Log attribute of the CL program.
4
All requests and all messages with a severity code greater than or equal to the severity specified, including trace messages and commands run by a CL program if allowed by the Log CL program commands job attribute and the Log attribute of the CL program.