CA Dynam for VSE User Guide
CA Dynam for VSE User Guide CA Dynam for VSE User Guide
Changing File Characteristics [ ,SORTIN= {(keys)|keyname } ] [ ,SORTOUT= {(keys)|keyname } ] [ ,SORTWRK=(filename,SYSnnn) ] [ ,SYSxxx ] IBM DLBL Parameters The IBM DLBL parameters are as follows: filename 'dataset-name' retention type Indicates the standard IBM DTF file name. Indicates the standard IBM data set name. Indicates the standard IBM retention period specification. Indicates the standard IBM access method type specification. If the DLBL type and/or retention are omitted, the commas following those fields must be supplied. CA Dynam/FI does not begin searching for its options until the fifth positional parameter. Valid (notice commas): // DLBL FILE,'TEST',NOTAPE Invalid (commas missing): // DLBL FILE,'TEST',NOTAPE But, if the first CA Dynam/FI operand is a keyword, you may omit commas when you omit retention and/or type, as shown: // DLBL FILE,'TEST',BLKSZ=OPT,NOTAPE IBM DLBL options Indicate the IBM DLBL optional parameters. (See previous note in relation to "type.") CA Dynam/FI Operands The remaining operands are as follows: BLKSZ= Specifies the block size for the file. It is either a decimal number between 1 and 65535, or the keyword OPTIMIZE (or OPT). If you specify OPTIMIZE, CA Dynam/FI recalculates the block size for the physical unit on which the data set resides. Note that this may not be the maximum block size for the device. When BLKSZ=OPT is specified, CA Dynam/FI uses the OPTBLKS value defined in the DYNAM/FI option record for disk files during the installation procedure. If full-track blocking was indicated, then the block size value is set to the approximate track size of the particular disk device type. For example, files on 3330 disks are given a block size value which is a multiple of the record length and as close to 13,030 bytes as possible. If you specify BLKSZ=OPT and the disk device type is FBA, the CISIZE, not the block size, is recalculated. With FBA, the block size will not be changed. 6–16 User Guide
Changing File Characteristics Before a file can be used as input with this specification, it must first be created with the BLKSZ=OPT option. If a file is created with CA Dynam/FI OPT blocking, then when the file is processed for input, either OPT or the correct numeric block size must be used. If you specify neither, unpredictable results can occur. Default: Block size defined in the Catalog or else block size in the user's program CONCAT Specifies that this file is to be concatenated with another file. When CONCAT is specified, a single open can be used to read two (or more) input files. Specify CONCAT on the label of each file to be concatenated, except for the last one to be read. CONCAT=ALL CONCAT=nn FIOPT=(options) Concatenates all versions of a data set. Concatenates the first nn versions of a data set. Specifies CA Dynam/FI options. Options may be listed in any order, separated by commas and enclosed in parentheses. AUDIT NOCNTRL NORELSE NOTRUNC RELEASE SB|DB VERIFY Instructs CA Dynam/FI to control processing of this file, even though nothing is to be changed, to get AUDIT information about the processing of the file. Ignores CNTRL requests for this file. For more information about the CNTRL macro, see the IBM Supervisor And I/O Macro manual. Ignores RELSE requests for this file. For more information about the RELSE macro, see the IBM Supervisor And I/O Macro manual. Ignores TRUNC requests for this file. For more information about the TRUNC macro, see the IBM Supervisor And I/O Macro manual. Releases the logical assignment for the file at close (applies only to temporary programmer logical units). Default: No release of the assignment. Single or double buffering for this file. Default: The buffering technique specified by the user program. Verifies output by reading the record just written. CA Dynam/FI enables the VERIFY option in the program DTF. Chapter 6: Controlling File Independence 6–17
- Page 249 and 250: Disk File Maintenance Utilities PAR
- 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: Changing File Characteristics SORTW
- Page 303 and 304: Changing File Characteristics SRTCO
- 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.
Changing File Characteristics<br />
Be<strong>for</strong>e a file can be used as input with this specification, it must first be<br />
created with the BLKSZ=OPT option. If a file is created with <strong>CA</strong> <strong>Dynam</strong>/FI OPT<br />
blocking, then when the file is processed <strong>for</strong> input, either OPT or the correct<br />
numeric block size must be used. If you specify neither, unpredictable results<br />
can occur.<br />
Default: Block size defined in the Catalog or else block size in the user's<br />
program<br />
CON<strong>CA</strong>T<br />
Specifies that this file is to be concatenated with another file.<br />
When CON<strong>CA</strong>T is specified, a single open can be used to read two (or more)<br />
input files. Specify CON<strong>CA</strong>T on the label of each file to be concatenated,<br />
except <strong>for</strong> the last one to be read.<br />
CON<strong>CA</strong>T=ALL<br />
CON<strong>CA</strong>T=nn<br />
FIOPT=(options)<br />
Concatenates all versions of a data set.<br />
Concatenates the first nn versions of a data set.<br />
Specifies <strong>CA</strong> <strong>Dynam</strong>/FI options. Options may be listed in any order, separated<br />
by commas and enclosed in parentheses.<br />
AUDIT<br />
NOCNTRL<br />
NORELSE<br />
NOTRUNC<br />
RELEASE<br />
SB|DB<br />
VERIFY<br />
Instructs <strong>CA</strong> <strong>Dynam</strong>/FI to control processing of this file,<br />
even though nothing is to be changed, to get AUDIT<br />
in<strong>for</strong>mation about the processing of the file.<br />
Ignores CNTRL requests <strong>for</strong> this file. For more in<strong>for</strong>mation<br />
about the CNTRL macro, see the IBM Supervisor And I/O<br />
Macro manual.<br />
Ignores RELSE requests <strong>for</strong> this file. For more in<strong>for</strong>mation<br />
about the RELSE macro, see the IBM Supervisor And I/O<br />
Macro manual.<br />
Ignores TRUNC requests <strong>for</strong> this file. For more<br />
in<strong>for</strong>mation about the TRUNC macro, see the IBM<br />
Supervisor And I/O Macro manual.<br />
Releases the logical assignment <strong>for</strong> the file at close<br />
(applies only to temporary programmer logical units).<br />
Default: No release of the assignment.<br />
Single or double buffering <strong>for</strong> this file. Default: The<br />
buffering technique specified by the user program.<br />
Verifies output by reading the record just written. <strong>CA</strong><br />
<strong>Dynam</strong>/FI enables the VERIFY option in the program DTF.<br />
Chapter 6: Controlling File Independence 6–17