CA TLMS

TLMSVMFV – The new VMF chaining utility for CA TLMS 12.6. 

Jul 21, 2015 03:21 PM

For years TLMSVCVS was the main source for finding volume chaining errors within the VMF.

With the CA TLMS 12.6 release, TLMSVMFV will replace TLMSVCVS. The major updates are:

 

  • Report on dataset chaining errors.  TLMSVCVS only reported on volume chaining errors.
  •   Ability to delay the reporting of open volumes.
  •   Multiple levels of detail reporting.
  •   Report on orphaned records.
  •   Summary of VMF usage.

 

TLMSVMFV is executed to verify the VMF using the same technique used by TLMSVMFU for the VMF utilities. The technique allows TLMSVMFV to verify VMF record chaining without "running the chains". This prevents I/O errors from bad chains and allows TLMSVMFV to continue verification of a chain after an error is detected. TLMSVMFV also finds orphaned records. Orphaned records are records which cannot be found by TLMS batch processing that starts with the beginning of a tape chain.   

We recommend running with a LEVEL of 5 and a DELAY of the number of days that your longest tape job will execute.

The scope of the verification and reporting is controlled by the following CATVMFV parameters:

 

DELAY

This parameter instructs TLMSVMFV to delay the verification of tape chains for the specified number of days. This prevents reporting of false errors for tapes which are being created while CATVMFV is running.

Specifies the number of days TLMSVMFV waits after the creation date before any given verification.

Range: 0 to 9999999 days

 

LEVEL

This parameter specifies the level of detail TLMSVMFV is to report. The LEVEL parameter can greatly reduce the size of the TLMS064 report. By default TLMSVMFV uses DELAY=3 and LEVEL=1. The report levels are: 

  • Level 1 is the default report level.
  • Level 5 and above print orphans records. These are records which are not connected to valid TLMS chains. These records are lost during a VMF RESTORE.
  • Level 9 is the most detailed report. Level 9 overrides the DELAY PARM. Level 9 can only be run against a VMF that has no activity.

 

Specifies the level of detail for verification and reporting. The lower the value of LEVEL the less detail produced.

Valid values: 1, 2, 5, and 9

            PRM keywords can be specified in any order and are separated by commas or blanks.

 

 

Modify the CATVMFV parameter for SORT to values similar to those in CATVMFU. These vary with the size of the VMF, for example:

SORTLIB='SYS1.SORTLIB'

SPCVMF='(CYL,(5,5))' 

WORK='SYSALLDA'

Specify the DELAY and LEVEL parameters via CATVMFV PRM=. For example:

CATVMFV PRM=’DELAY=6  LEVEL=5’

 

Return codes and error messages from TLMSVMFV.

 

Return Code 4 - Completed with warning:

CAT6402W ORPHANED MVL. CURR VSN(vvvvvv) CHAIN-ID(iiiiiiii)

CAT6403W ORPHANED MDS. CURR VSN(vvvvvv) CHAIN-ID(iiiiiiii)

CAT6420W UNCHAINED VOLUME HAS FIELD(S) SHOWING CHAINING

CAT6430W VOLCNT(NNN) IS LESS THAN VOLSEQ(NNN)

CAT6431W CHAIN BASE MUST BE VOLUME SEQUENCE 1

CAT6436W CHAIN BASE MUST BE FILE SEQUNCE 1

CAT6437W VSN OF CHAIN BASE MUST EQUAL CHNVOL

CAT6438W CHAIN BASE MUST HAVE NON-ZERO CHAIN-ID

CAT6439W CHAIN BASE HAS NO DATA SETS OR VOLUMES CHAINED

CAT6440W VOLCNT(nnn) NOT EQUAL VOLUMES CHAINED(nnn)

CAT6449W VOLSEQ(NNN) LARGER THAN VOLUMES CHAINED(NNN)

CAT6459W VOLSEQ OF CHAINED VOLUME NOT GREATER THEN 1 

 

Return Code 8 - Error before attempt:

CAT6404E VOLSEQ IS NOT PACKED, ZERO USED FOR PROCESSING

CAT6405E VOLSEQ IS NOT PACKED, ZERO USED FOR PROCESSING

CAT6407E VOLSER NOT LOCATED IN CURRENT MULTI-VOLUME CHAIN

CAT6408E CHNVOL DOES NOT MATCH CURRENT CHNVOL(vvvvvv)

CAT6409E CHAIN-ID DOES NOT MATCH CURRENT CHAIN-ID(iiiiiiii)

CAT6412E INVALID RETURN CODE FROM SORT - RC=XX

CAT6414E ORPHANED VSN. VOLUME CONTAINS fffff FILES

CAT6416E VOLUME FSQ IS BAD IT SHOULD BE hhhhh

CAT6417E MDS FSQ IS fffff SHOULD BE hhhhh

CAT6418E VOLSER MISSING FROM MULTI-VOLUME CHAIN

CAT6421E CHAINED VOLUME WITH FIELD(S) SHOWING NOT CHAINED

CAT6432E THE FIRST MVL POINTER IS ZERO BUT THE LAST IS NOT

CAT6433E THE LAST MVL POINTER IS ZERO BUT THE FIRST IS NOT

CAT6434E THE FIRST MDS POINTER IS ZERO BUT THE LAST IS NOT

CAT6435E THE LAST MDS POINTER IS ZERO BUT THE FIRST IS NOT

CAT6441E 1ST MDS PTR IN BASE DOES NOT POINT TO THIS MDS

CAT6442E THIS MDS DOES NOT POINT TO PREV MDS

CAT6443E PREV MDS DOES NOT POINT TO THIS MDS

CAT6444E PREVIOUS RECORD IS NOT AN MDS RECORD

CAT6445E LAST MDS PTR IN BASE DOES NOT POINT TO THIS MDS

CAT6446E THIS MDS DOES NOT POINT TO NEXT MDS

CAT6447E NEXT MDS DOES NOT POINT TO THIS MDS

CAT6448E NEXT RECORD IS NOT AN MDS RECORD

CAT6451E 1ST MVL PTR IN BASE DOES NOT POINT TO THIS MVL

CAT6452E THIS MVL DOES NOT POINT TO PREV MVL

CAT6453E PREV MVL DOES NOT POINT TO THIS MVL

CAT6454E PREVIOUS RECORD IS NOT AN MVL RECORD

CAT6455E LAST MVL PTR IN BASE DOES NOT POINT TO THIS MVL

CAT6456E THIS MVL DOES NOT POINT TO NEXT MVL

CAT6457E NEXT MVL DOES NOT POINT TO THIS MVL

CAT6458E NEXT RECORD IS NOT AN MVL RECORD

 

Return Code 12 - Error after attempt:

CAT6400E ERROR PARSING INPUT PARAMETERS

CAT6401E RELEASE 5.3 AND 5.4 VMFS ARE NOT SUPPORTED

 

Return Code 16 - Unable to continue:

CAT6415E - REQUIRED FILE NOT OPEN. ABORTING!

CAT6499I PROGRAM IS TERMINATING

Statistics
0 Favorited
1 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.