Information Gathering › Run the Logging Script

Run the Logging Script

We provide the ETJLOGC job to help you quickly gather key diagnostic information when issues arise. Use this procedure when you detect an unexpected CA Chorus condition. You can run this job on your own or at the request of a CA support technician.

Before you can run this job, note the following prerequisites:

• Your user ID must be in the CHORGRP group.
• You must have write authority.
• You can run this job anytime after a deployment is complete. However, log files only exist after the server has started and in some cases, certain functions exercised. Configuration files will exist after the particular configuration tasks are completed.

For various reasons, a file may not exist even though a discipline is installed. Unfound files result in a message that begins with Log or Configuration. If no one has used the function that creates a log file, the log files may not exist. Configuration files exist if the CA Chorus discipline has been configured.

Note: If you encounter several CA Chorus errors, run EJTLOGC immediately. This timely saving of these files can provide better data because less extraneous data is included.

Follow these steps:

1. Edit ETJLOGC from the CETJJCL library. Follow the instructions in the member. 
2. Save these changes, and submit the job.

   Note: If you experience another issue such that you must send files to support, run this job without any further editing. 

   The job ends with condition code 0. The job output lists a number of pax files. These files reside in the /cai/cetjr4m0/CASupport directory. After you open an issue with CA Support, FTP the files in this directory to the CA Support SFTP site. 

   The output includes two files:

   collections details

   Lists the installed disciplines, the accessed directories, and which files are included in the pax files or which files were not found.

   collection log

   Lists warnings about improper variable settings or other items to correct.

3. FTP the z/OS output from the CHORJBOS task and the ENVETJ file from the CETJOPTN library.

Example FTP Steps

Use the sample with these steps. 

1. Create an FTP file.
2. Replace the items in brackets with site-specific values.
3. Create a folder to hold the files (for example, FTP2CA).
4. Change directories to this folder (for example, cd FTP2CA).
5. Execute ftp –s:../example1.ftp > ../ftp1.log
6. Check that the files in FTP2CA are the same as the files listed in the output of ETJLOGC. 
7. Transfer the contents of FTP2CA to the CA Support SFTP site for the issue.

Sample File for FTP Example

open [hostname]

[userid]

[password]

cd [chorus_install_home]/logs/CASupport

bin

PROMPT

mget *.pax

mget collection*

quit

More information:

Gather Data for zFS File Systems

Debug the Web Crawler in the Knowledge Center