Necessary documentation for IBM service

Diagnosing problems with zCX requires information from various sources. IBM Service will frequently request this information. This section describes the artifacts that will be requested by IBM Service for any zCX problems.

First, take note of the different pieces that make up zCX:
Table 1. zCX composition
zCX component FMID COMPID FESN
zCX server HZDC7C0 5752SCCDE 0509651
zCX virtual base HBB77C0 5752SCCON 0501283
zCX workflows HZDC7C0 5752SCCWF 0501251

SVC Dump

This dump is typically produced automatically by the system. If the code has ABENDed, this will be created and available for retrieval in the usual place as defined by the installation. zCX uses normal z/OS processing to create and handle this dump.

It may be necessary to create a console dump of the zCX address space. This also follows existing z/OS processes. zCX will automatically collect the appropriate information into the dump when the following is issued to the z/OS system console:
DUMP COMM=(Mydump)
R xx, JOBNAME=job_name 

CTRACE information

The collection of CTRACE information is controlled by a zCX CTRACE parmlib member. More information on CTRACE can be found in the Reference materials for zCX chapter of this document.

JES joblog

zCX is a started task that will create a job in JES like any other job on the system. This joblog will be available on the jes spool. Use the procedures associated with your system to capture the joblog for the zCX instance in question.

zCX Server Instance Directory FFDC

Kernel panic errors will automatically reboot the instance and produce FFDC data. Some errors in the appliance will not automatically reboot the instance. When this is the case, FFDC data will be produced the next time the instance is instantiated. Typically, the appliance will fail to reboot the second time in those circumstances.

A GLZM008I message will be produced when the appliance has created FFDC data. An additional message GLZM009I will be produced to indicate where this data has been stored. It will be found in the server instance directory associated with the appliance and will have the file name as indicated in the message.

If IBM Service requests these logs, either FTP them from your z/OS image as binary files, or use the TSO OGET command with the BINARY parameter to export them to a data set.

Example:
13.02.34 S0271400  GLZB001I zCX instance ZCXRLK initialization is complete. Code date 07/18/19.
13.02.35 S0271400  GLZM008I zCX instance ZCXRLK is storing failure data for appliance  681     
   681             alert:                                                                      
   681             AZDL0004E At least one prior boot failed                                    
13.02.35 S0271400  GLZM009I zCX instance ZCXRLK stored failure data:  682                      
   682             Size=36864                                                                  
   682             Checksum=172244767                                                          
   682             File Name=NP8-2019-08-02T17_02_35-AZDL0004E-BL2_error.tar                   
   682             Directory=/oc4z/shared/zcx_instances/ZCXRLK/FFDC                            
13.02.43 S0271400  GLZB002I zCX instance ZCXRLK has ended.  683                                
13.02.45 S0271400  GLZB005I z/OS system service GLZBAIN failed, RC=0000000C RSN=01010016  693  
   693             zCX ended due to failure.                                                   
13.02.45 S0271400  IEF404I ZCXRLK - ENDED - TIME=13.02.45                                      
13.02.45 S0271400  $HASP395 ZCXRLK   ENDED - RC=0012

Example of zCX instance error

This example produced both FFDC information from the appliance and an ABEND from zCX. When reporting this type of problem, send the FFDC file, the dump, and the JES joblog to IBM Service.
11.04.15 S0269997  GLZB001I zCX instance ZCXRLK initialization is complete. Code date 07/18/1
11.04.17 S0269997  GLZM008I zCX instance ZCXRLK is storing failure data for appliance  815   
   815             alert:                                                                    
   815             AZDL0001E Unexpected error 2A5A044C, rsn1=00000060 rsn2=00000201          
11.04.17 S0269997  GLZM009I zCX instance ZCXRLK stored failure data:  816                    
   816             Size=36864                                                                
   816             Checksum=750364863                                                        
   816             File Name=NP8-2019-08-02T15_04_17-2A5A044C-BL1_error.tar                  
   816             Directory=/oc4z/shared/zcx_instances/ZCXRLK/FFDC                          
11.04.25 S0269997  IEA794I SVC DUMP HAS CAPTURED:  823                                       
   823             DUMPID=003 REQUESTED BY JOB (ZCXRLK  )                                    
   823             DUMP TITLE=COMPON=GLZ,COMPID=5752SCCON,ISSUER=GLZMIREC,MODULE=G           
   823                        LZBATCB+00000502,ABEND=S0C0D,REASON=8004000F                   
   823             DUMP CAPTURED USING OPTIMIZE=YES                                          
11.04.25 S0269997  GLZB002I zCX instance ZCXRLK has ended.  824                              
11.04.26 S0269997  GLZB005I z/OS system service GLZBAIN failed, RC=0000000C RSN=01010015  841
   841             zCX ended due to failure.                                                 
11.04.27 S0269997  IEF404I ZCXRLK - ENDED - TIME=11.04.27                                    
11.04.27 S0269997  $HASP395 ZCXRLK   ENDED - RC=0012