NetViewGather: Dumping Canzlog archive datasets

Answer

There are three Canzlog datasets that need to be sent in for review.

1. Canzlog Master Index (one): archive.hlq.NV.CANZLOG.INDEX
2. Canzlog Archive Index dataset (one): archive.hlq.DXdddddd.HRxxxxxx
3. Canzlog Archive Message datasets (many): archive.hlq.CZdddddd.Txxxxxx

note: There is a video attached to this technote explaining this process as well.

note: archive.hlq is defined in CNMSTYLE/CNMSTGEN

You can also issue NetView command 'LIST STATUS=CANZLOG' to see the archive.hlq. In this example, the archive.hlq is set to 'USER.V6R2'

Use the following JCL to have the DFSMS ADRDSSU utility dump the Canzlog files into a single dataset. Be sure to change the archhlq to your archive.hlq

The JCL will dump all three of the Canzlog Archive datasets into one dataset defined in DD TO.

//DUMPARCH JOB MSGCLASS=A,CLASS=A,MSGLEVEL=(1,1)                    
//* JCL used to dump out Canzlog Archive Datasets                    
//STEP1   EXEC PGM=ADRDSSU,REGION=200M                              
//SYSPRINT  DD SYSOUT=A                                              
//*                                                                  
//* This is the dataset that the Archive datasets will get          
//* dumped into.                                                    
//* For calculating space:                                          
//*   Canzlog archive index data set is typically 6 TRKs in size    
//*   Canzlog archive message data set is typically 11 CYLs in size  
//*                                                                  
//TO     DD  DISP=(NEW,CATLG),                                      
//           DSN=arch.dump.data.set,VOL=SER=vvvvvv,                  
//           SPACE=(CYL,(nnn,mmm),RLSE),UNIT=unit                    
//*                                                                  
//* archhlq is the high level qualifier defined for the Canzlog      
//* archive as shown in 'LIST STATUS=CANZLOG' HLQ parm              
//* The OUTDD will dump the following datasets:                      
//* archhlq.NV.CANZLOG.INDEX   - CANZLOG master index file          
//* archhlq.DXdddddd.HRnnnnnn  - CANZLOG index files                
//* archhlq.CZdddddd.Tnnnnnnn  - CANZLOG message file                
//*                                                                  
//SYSIN  DD  *                                  
  DUMP OUTDD(TO) -                              
       DS(INCLUDE(archhlq.NV.CANZLOG.INDEX, -    
                  archhlq.DX%%%%%%.**, -        
                  archhlq.CZ%%%%%%.**)) -        
       ALLDATA(*) -                              
       TOL(ENQF)                                
/*                                              

note: I have included the JCL in a Text document attached to this Technote for easy cut and paste

Be sure to issue NetView command 'CANZLOG CUE' prior to dumping the Canzlog Archive files. The command forces recent messages from the Canzlog to be written to the Archive files. This will ensure the most recent entries are included in the Archive files.

The JCL example will dump out all of the Canzlog message files on the catalog as coded CZ%%%%%%. The percent sign '%' is a wildcard.
The number of Canzlog Message files to be dumped can be filtered to avoid sending in irrelevant datasets. The CZddddd qualifier on the dataset name is the date. Take this dataset name for example:
USER.V6R2.CZ161018.T132628
CZ161018 is in format YYMMDD, so the dataset is from 2016, October (10) the 18th. Here are some examples on how to limit the number of message files dumped:

• archhlq.CZ16%%%%.** will dump all message files from 2016
• archhlq.CZ1610%%.** will dump all msg files from of October 2016
• archhlq.CZ161018.** will dump message files for October 18th 2016.

You can review the job output and verify that the required Canzlog datasets were dumped into the TO dataset.

Please TERSE the TO dataset prior to FTP into ECUREP. This will ensure that the dataset contents are not corrupted during transfer.