CA Dynam for VSE User Guide

CA Dynam for VSE User Guide CA Dynam for VSE User Guide

supportcontent.ca.com
from supportcontent.ca.com More from this publisher
03.03.2015 Views

DYNCAT Commands NO Removes all options. USerid= Optional parameter. Changes the user ID field. Valid entries are: a 2-character ID to be used for reporting purposes. NO removes user ID value. VERsion|VOLser|GDSid VERsion= VOLser= GDSid= Optional parameter. Specifies the generation to be modified. The VERSION number, VOLSER number, or GDSID operand must be present when altering a specific generation. Valid entry is a 1- to 3-digit number in the range 1-999. Optional parameter. Specifies the first or only volume of a dataset generation to be modified. The VOLser number, VERsion number, or GDSid operand must be present when altering a specific generation. Valid entry is a 1- to 6-character volume serial number. Optional parameter. Specifies the Generation Data Set ID of the disk dataset to be modified (CA Dynam/D controlled only). The GDSid, VERsion number, or VOLser number operand must be present when altering a specific generation. Valid entry is a 1- to 2-digit numeric generation ID (1 - 99). VIRTape= Optional parameter. Specifies whether a dataset should be created as a virtual file. NO VTAPE FTAPE The file is not created as a virtual file. The file is created using VTAPE. The file is created using FakeTape. VLTloc= Optional parameter used to change the vault location for each version of the dataset. Valid entry is a 1- to 999-alphabetic characters enclosed in parentheses and separated by commas. Each character represents a vault location. Its relative position in the string represents the generation of the dataset that is to be in that vault. Specify NO to clear. For example: (A,A,B,A) specifies that versions 1 and 2 are to be in vault A. Version 3 is to go to vault B and version 4 is to return to vault A. The first 999 versions of a dataset may have vault location control. All versions after 999 will be kept in vault A. If a version is specified, the version will be moved to the vault specified. 8–34 User Guide

DYNCAT Commands VLTSEQ= VOLID= WORK= Optional parameter used to specify the starting version for the VLTLOC parameter. VLTSEQ must be specified sequentially with no gaps in versions. Valid entries are 1 through 999. Optional parameter. Defines a volume identifier that allows the tape volume to receive output from the dataset. The volume identifier must match the first two characters of the volume serial number. Optional parameter. Indicates whether this dataset is to be processed as a tape work dataset. Valid entries are: YES NO This is a work dataset. This is not a work dataset. Examples Examples are shown next. // JOB ALTER THE CA Dynam CATALOG // EXEC DYNCAT,SIZE=128K ALTER 'SALESTRANS' NGEN=3 LENGTH=S CLOSE=UNL ALTER 'PAYMAST' VERS=1 LOCK ALTER 'AR SUSPENSE' EXPDATE=RT+14 VOLSER=(486) ALTER 'AP DAILY' WORK=NO PED=**/31/** PEDCYC=3 ALTER 'CUSTMAST' PASSWORD='CUSTOMER' NEWPSWD='' ALTER 'EOM.TRANS.FILE' ALLOC=(POOL01,TRK,39,19,3) ALTER 'FIXED.FILE' PRIME=(0,SYSRES,ABS,1938,57) ALTER 'VAULT.DSN' VLTLOC=(A,B,C,D,E) ALTER 'VAULT.DSN' VLTLOC=(F,G,A,B,C) VLTSEQ=6 ALTER 'VAULT.DSN' VLTLOC=(D,E,F,G) VLTSEQ=11 /* /& 1. This sets the number of generations to be retained for SALESTRANS to 3.It also sets the length code to short and forces the dataset to be rewound and unloaded at close. 2. This locks Version 1 of PAYMAST so that it cannot be read. 3. This adds 14 days to the expiration date of AR SUSPENSE on volume 486. 4. This changes AP DAILY from a work file to one using automatic as-of-date control and retaining 3 as-of-date versions. 5. This removes the password from CUSTMAST. 6. This changes the disk allocation specified for 'EOM.TRANS.FILE' to a primary allocation of 39 tracks, on volser POOL01, and three secondary allocations of 19 tracks each. Chapter 8: Maintaining the Catalog−DYNCAT Program 8–35

DYN<strong>CA</strong>T Commands<br />

NO<br />

Removes all options.<br />

USerid=<br />

Optional parameter. Changes the user ID field. Valid entries are:<br />

a 2-character ID to be used <strong>for</strong> reporting purposes.<br />

NO removes user ID value.<br />

VERsion|VOLser|GDSid<br />

VERsion=<br />

VOLser=<br />

GDSid=<br />

Optional parameter. Specifies the generation to be<br />

modified. The VERSION number, VOLSER number, or<br />

GDSID operand must be present when altering a specific<br />

generation. Valid entry is a 1- to 3-digit number in the<br />

range 1-999.<br />

Optional parameter. Specifies the first or only volume of<br />

a dataset generation to be modified. The VOLser number,<br />

VERsion number, or GDSid operand must be present<br />

when altering a specific generation. Valid entry is a 1- to<br />

6-character volume serial number.<br />

Optional parameter. Specifies the Generation Data Set ID<br />

of the disk dataset to be modified (<strong>CA</strong> <strong>Dynam</strong>/D<br />

controlled only). The GDSid, VERsion number, or VOLser<br />

number operand must be present when altering a specific<br />

generation. Valid entry is a 1- to 2-digit numeric<br />

generation ID (1 - 99).<br />

VIRTape=<br />

Optional parameter. Specifies whether a dataset should be created as a virtual<br />

file.<br />

NO<br />

VTAPE<br />

FTAPE<br />

The file is not created as a virtual file.<br />

The file is created using VTAPE.<br />

The file is created using FakeTape.<br />

VLTloc=<br />

Optional parameter used to change the vault location <strong>for</strong> each version of the<br />

dataset. Valid entry is a 1- to 999-alphabetic characters enclosed in<br />

parentheses and separated by commas. Each character represents a vault<br />

location. Its relative position in the string represents the generation of the<br />

dataset that is to be in that vault. Specify NO to clear.<br />

For example: (A,A,B,A) specifies that versions 1 and 2 are to be in vault A.<br />

Version 3 is to go to vault B and version 4 is to return to vault A. The first 999<br />

versions of a dataset may have vault location control. All versions after 999<br />

will be kept in vault A. If a version is specified, the version will be moved to<br />

the vault specified.<br />

8–34 <strong>User</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!