//stepname EXEC PGM=TMSXTEND,REGION=0M, // PARM='parm1,parm2 ' //TMSRPT80 DD SYSOUT=* /* TMSBLDVR RPT */ //TMSRPT81 DD SYSOUT=* /* TMSAUDEX RPT */ //SYSPRINT DD SYSOUT=* /* IDCAMS OUTPUT */ //CAISNP DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSIN DD * ADDVOL 001800-001899 ROBTY=02 VENDOR=BASF ADDVOL VM5000-BM5099 /* adding a second range */ REMVOL VT0100-VT0199 /* sample of removing a volume range */ ADDDSNB 1000 /* //CPULIST DD * EXCLUDE CPU9 /* this is a test system we are removing */ INCLUDE CPU6 /* PROD system with no tape activity */ /*
Parameter Definitions
The DIAG parameter can be specified alone or with the TEST or RECOVER parameter. Parameters may be specified in any order and separated by commas or blanks. If the RECOVER parameter is omitted the program will execute in extend mode.
This parameter causes TMSXTEND to write diagnostic snap dumps to the CAISNP output. Snap dumps are created to display internal volume tables, key data areas and changes to control records.
This parameter causes TMSXTEND to run in recovery mode. In recovery mode TMSXTEND will determine the status of a failed extend. If the signal to switch to the new TMC has not yet been given to all CPU's sharing the TMC, it will rename and return the old TMC to its original status, updating any control records necessary. If the signal to switch to the new TMC has been given to all CPU's sharing the TMC, it will finish updating any control records necessary.
This parameter causes TMSXTEND to run in test mode. In test mode, TMSXTEND will perform all of the checks and most of the functions of the actual extend mode. The new TMC is created and synchronized but the TMCs are not renamed and the CPUs do not switch to the new TMC. This mode allows you to preview or test the extend process. In test mode, if errors are detected they will be reported but the process does not fail as it does with an actual extend.
JCL Considerations
Note: The JCL provided in this document assumes that the CA 1 load library is defined as a LINKLIST data set.
Defines the report output data set for the TMS REPORT-80. This DD statement is required.
Defines the report output data set for the TMS REPORT-81. This DD statement is optional.
Defines the report output data set used by IDCAMS, which is invoked to perform the TMC renames. This DD statement is required.
TMSXTEND writes snap dumps to this DD statement when requested by PARM=DIAG. This DD statement is required only if PARM=DIAG is specified.
Defines the input data set for volume range and DSNB control statements. This DD statement is optional. If you do not specify a SYSIN DD statement all volume ranges and DSNBs in the existing TMC will be copied to the new TMC. This approach may be used to copy a TMC to a new, blocked TMC without adding or removing any volume ranges.
Defines the input data set for CPU include or exclude control statements. This DD statement is optional and if not specified, all CPUs sharing the TMC must be found in the current Audit file.
Completion Codes
The following completion codes are issued by TMSXTEND:
Successful completion.
TMC extend failed. Refer to the TMS REPORT-80 or 81 reports and the job log to determine cause of failure.
Invalid control statement error. Check TMS REPORT-80 or 81 to determine cause of failure.
The current TMC could not be allocated. Check to insure that the TMC is cataloged on the system where you are running TMSXTEND.
The new TMC could not be allocated or opened. Refer to messages TMSVR03E or TMSVR05E in the chapter "Utility Report Messages" in the Message Reference Guide.
TMSXTEND had abended for one of many reasons.Refer to the abend codes in the section IEFTMS83 - SMF Abend in the chapter "Abend Codes" in the Message Reference Guide.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|