CA Dynam for VSE User Guide
CA Dynam for VSE User Guide CA Dynam for VSE User Guide
Changing File Characteristics FIVSAM, NOFIVSAM IGNore Specifies whether CA Dynam/FI is allowed to convert the file to a VSAM file if a VSAM DLBL record is found. This parameter overrides the default set in the DYNAM/FI option record. (Note that if FIVSAM is specified, CA Dynam/FI, rather than VSAM/SAM, performs the modification from SD to VSAM by creating ACB/RPL.) Signals that ignore processing is in effect. The file is not opened. For input, an EOF (end-of-file record) will be returned at the first GET/READ. For output, all PUTs/WRITEs will be discarded. CA Dynam/FI IGNORE processing is an alternative to the IBM 'ASSGN IGN' facility. If, in normal processing, the logical unit derived by DYNAM/FI is assigned 'IGN', but the DLBL has the CA Dynam/FI 'IGN' option, CA Dynam/FI processing will prevail; i.e, the IBM facility will be ignored. This option is not supported for DTFDA (VCKD) or for CA SORT input/output files. LRECL=nnnnn Defines the logical record length for the file. Default: Record length defined in the Catalog or else record length in the user's program. MAXCI=nnnnn Specifies the maximum CI size to be used for FBA devices to calculate a new CISIZE with BLKSZ=OPT. When BLKSZ=OPT and the device pointed to is FBA, the block size is not changed but the DTF CISIZE field gets a computed value based on MAXCI parameters. nnnnn must be a valid FBA CI size or zero. If this operand is specified but the device pointed to is not FBA, it will be ignored. Default: Control interval size specified at installation. NOFI NOTAPE RECFM=xx Ignores CA Dynam/FI processing for this file (used with programs such as DITTO, which modifies its DTF after OPEN processing is complete). Prevents the operator from switching to TAPE for this generation of the disk file. Overrides the Catalog specification of FI for this data set. Specifies the record format for the file. Record formats supported are: F FB V VB U Fixed Fixed-blocked Variable Variable-blocked Undefined Default: Record format in the Catalog or else format remains unmodified. 6–18 User Guide
Changing File Characteristics SRTCORE=nnnnnn Specifies the amount of storage, in bytes, which CA SRAM is to use for this particular task. (Multiple tasks are permitted.) System performance may be enhanced by providing a specific storage size. Default: Twice calculated minimum. SORTIN=, SORTOUT= Requests CA SRAM for dynamic file sorting, and defines both when the file is to be sorted (input, output, or both) and the sort key fields to be used for each. The sort fields may be specified in the normal CA SRAM key definition vector format, or as the name of a predefined Catalog sort key entry. The use of the cataloged keyname format is recommended since it provides maximum flexibility. With this format, the file may be sorted using many different sort keys without complex job control using continuation statements. It also permits changing sort key fields without job control modification, and it allows many files to share the sort key definitions. For more information about maintaining sort key names, see the DYNCAT ALTER and DEFINE commands. =(keys) s l t Specifies each key field/vector, composed of four parameters, (s1,l1,t1,m1,s2,l2,t2,m2,...) relative field start position in the data record key field length in bytes sort key type: C/CH B/BI P/PD alphanumeric characters positive binary data packed decimal data m collating sequence required: A D ascending sequence descending sequence =keyname Identifies a Catalog Sort Key Record (SKNAME) containing the sort key vector to be used for sorting the file. SORTWRK= Specifies the file name (maximum of 5 characters) of the label information which is to be used as the CA SRAM work file. SYSnnn is the logical unit to be used in accessing the file. If more than one dynamically sorted file is processed in a single program, this parameter must be used to define the CA SRAM work files. Naturally, more than one task cannot use the same work file at the same time. Chapter 6: Controlling File Independence 6–19
- Page 251 and 252: Disk File Maintenance Utilities R
- Page 253 and 254: Disk File Maintenance Utilities Y N
- Page 255 and 256: Disk File Maintenance Utilities CHA
- Page 257 and 258: Disk File Maintenance Utilities Opt
- Page 259 and 260: Disk File Maintenance Utilities OPE
- Page 261 and 262: Disk File Maintenance Utilities You
- Page 263 and 264: Disk File Maintenance Utilities Not
- Page 265 and 266: Disk File Maintenance Utilities '*'
- Page 267 and 268: Disk File Maintenance Utilities •
- Page 269 and 270: Disk File Maintenance Utilities Usi
- Page 271 and 272: Disk File Maintenance Utilities STO
- Page 273 and 274: Disk File Maintenance Utilities EXC
- Page 275 and 276: Disk File Maintenance Utilities •
- Page 277 and 278: Reporting on Disk Files The VTOCS r
- Page 279 and 280: Reporting on Disk Files • If VOL=
- Page 281 and 282: Reporting on Disk Files On the VOLF
- Page 283 and 284: Reporting on Disk Files • If VOL=
- Page 285 and 286: Chapter 6: Controlling File Indepen
- Page 287 and 288: Physical Files Physical Files The f
- Page 289 and 290: Unit Record Simulation Example // D
- Page 291 and 292: Unit Record Simulation CICS Macro L
- Page 293 and 294: Dynamic File Sorting CA SRAM normal
- Page 295 and 296: Changing File Characteristics TLBL
- Page 297 and 298: Changing File Characteristics NOTRU
- Page 299 and 300: Changing File Characteristics SORTW
- Page 301: Changing File Characteristics Befor
- Page 305 and 306: Changing File Characteristics Consi
- Page 307 and 308: Changing File Characteristics old b
- Page 309 and 310: Changing File Characteristics The i
- Page 311 and 312: Controlling System Actions DYNAMFI=
- Page 313 and 314: Controlling System Actions Note tha
- Page 315 and 316: Controlling System Actions BG 0000
- Page 317 and 318: Controlling System Actions BG 0000
- Page 319 and 320: Operator Device Switching Facility
- Page 321 and 322: Using Other Software with CA Dynam/
- Page 323 and 324: Using Other Software with CA Dynam/
- Page 325 and 326: Using Other Software with CA Dynam/
- Page 327 and 328: Direct Access File Independence Fac
- Page 329 and 330: Direct Access File Independence Fac
- Page 331 and 332: Direct Access File Independence Fac
- Page 333 and 334: Direct Access File Independence Fac
- Page 335 and 336: Direct Access File Independence Fac
- Page 337: Catalog Support for CA Dynam/FI The
- Page 340 and 341: Introduction to the File Management
- Page 342 and 343: Global Display Command Summary Glob
- Page 344 and 345: DYNCAT Command Panel ID Description
- Page 346 and 347: Accessing the File Management Syste
- Page 348 and 349: System Options Select Option To 3.
- Page 350 and 351: Data Set Maintenance Enter data spe
Changing File Characteristics<br />
SRTCORE=nnnnnn<br />
Specifies the amount of storage, in bytes, which <strong>CA</strong> SRAM is to use <strong>for</strong> this<br />
particular task. (Multiple tasks are permitted.) System per<strong>for</strong>mance may be<br />
enhanced by providing a specific storage size.<br />
Default: Twice calculated minimum.<br />
SORTIN=, SORTOUT= Requests <strong>CA</strong> SRAM <strong>for</strong> dynamic file sorting, and defines both when the file is<br />
to be sorted (input, output, or both) and the sort key fields to be used <strong>for</strong><br />
each. The sort fields may be specified in the normal <strong>CA</strong> SRAM key definition<br />
vector <strong>for</strong>mat, or as the name of a predefined Catalog sort key entry.<br />
The use of the cataloged keyname <strong>for</strong>mat is recommended since it provides<br />
maximum flexibility. With this <strong>for</strong>mat, the file may be sorted using many<br />
different sort keys without complex job control using continuation statements.<br />
It also permits changing sort key fields without job control modification, and it<br />
allows many files to share the sort key definitions. For more in<strong>for</strong>mation about<br />
maintaining sort key names, see the DYN<strong>CA</strong>T ALTER and DEFINE commands.<br />
=(keys)<br />
s<br />
l<br />
t<br />
Specifies each key field/vector, composed of four<br />
parameters, (s1,l1,t1,m1,s2,l2,t2,m2,...)<br />
relative field start position in the data record<br />
key field length in bytes<br />
sort key type:<br />
C/CH<br />
B/BI<br />
P/PD<br />
alphanumeric characters<br />
positive binary data<br />
packed decimal data<br />
m<br />
collating sequence required:<br />
A<br />
D<br />
ascending sequence<br />
descending sequence<br />
=keyname<br />
Identifies a Catalog Sort Key Record (SKNAME)<br />
containing the sort key vector to be used <strong>for</strong> sorting the<br />
file.<br />
SORTWRK=<br />
Specifies the file name (maximum of 5 characters) of the label in<strong>for</strong>mation<br />
which is to be used as the <strong>CA</strong> SRAM work file. SYSnnn is the logical unit to be<br />
used in accessing the file. If more than one dynamically sorted file is<br />
processed in a single program, this parameter must be used to define the <strong>CA</strong><br />
SRAM work files. Naturally, more than one task cannot use the same work file<br />
at the same time.<br />
Chapter 6: Controlling File Independence 6–19