CA Dynam for VSE User Guide
CA Dynam for VSE User Guide CA Dynam for VSE User Guide
Changing File Characteristics Concatenated Data Sets CA Dynam/FI provides an input data set concatenation facility. This facility allows multiple input data sets to be read as if they were a single data set, in response to a single open issued by the application. Concatenation is invoked by specifying the CONCat option on the label of each data set which is to be concatenated. Multiple concatenated input files may be processed concurrently; that is, an application that issues opens for several different data sets may use concatenation for one or all of them. In the case of tapes, the data sets to be concatenated may be single file data sets or part of multifile data sets, and may each consist of a single or multiple volumes. Input data sets to be concatenated may have different attributes. Data sets may be concatenated without regard to disk or tape residence, varying record formats, blocksizes, or logical units, as these attributes are resolved as part of normal CA Dynam/FI processing in a manner transparent to the application. The following sample JCL demonstrates concatenation: // JOB CONCATEX /* /* PROCESS MONTHLY A/P TRANSACTIONS /* /* INPUT: 1 CONCATENATED DATASET /* CONSISTING OF 2 TAPE DATASETS /* AND 2 DISK DATASETS /* // TLBL INPUT,'TRANS.TAPE.OLDEST',,CONCAT // TLBL INPUT,'TRANS.TAPE.OLDER',,CONCAT // DLBL INPUT,'TRANS.DISK.OLD',,,CONCAT // DLBL INPUT,'TRANS.DISK' // EXEC APMTHLY /& Where other CA Dynam products are installed, the concatenated data sets may be either controlled, uncontrolled, or a mixture of the two. All processing options supported by the other products in the CA Dynam family are supported for use in conjunction with concatenation. In addition, all versions of a particular data set may be read by using CONCAT=ALL or the first nn versions may be concatenated by using CONCAT=nn on the TLBL or DLBL. Additional Examples In this example, COBOL program COBTEST is originally written to read from a card reader (DTFCD) and write the output to a line printer (DTFPR). However, with CA Dynam/FI, the program will read from a tape file labeled 'CARD- INPUT' and write to a tape file labeled 'PRINT-OUTPUT'. 6–24 User Guide
Changing File Characteristics The input tape file is FISYSIN and the output tape file is FISYSLS. The output file generated is a standard labeled tape. Logical unit SYS001 is used for the SYSIN file and SYS002 for the SYSLST file. // JOB TEST1 // TLBL FISYSIN,'CARD-INPUT',,SYS001 // TLBL FISYSLS,'PRINT-OUTPUT',,SYS002,FIOPT=(SL) // ASSGN SYS001,TAPE // ASSGN SYS002,TAPE // EXEC COBTEST,SIZE=100K The file name is derived from: • DTFname in Assembler programs • File SELECT in COBOL programs. By default, the logical unit name is used. Example // DLBL SYS001, ... Recalculate the block size of an output disk file. Note that the block size of the disk file is calculated based upon the OPTBLKS value defined in the DYNAM/FI option record at installation time. For fixed-length records, the block size value is always a multiple of the record size value specified. // DLBL OUTPUT,'DISK-FILE',,SD,BLKSZ=OPT Reblock a tape file and set the options. The file below is reblocked on a tape to 8000 bytes, and double buffering is specified (DB). In addition, a rewind and unload operation is performed on the tape when it is closed (RUN). // TLBL OUTPUT,'TAPE-FILE',,BLKSZ=8000,FIOPT=(RUN,DB) Create a tape file and change the logical unit. Logical unit SYS018 is used to override the logical unit specified in the user's program. // TLBL TAPDISK,'TAPE-DISK',,SYS018 Read a disk file created with reblocked size. Note that if the block size operand were omitted, the block size value would default to the one in the user's program. In many cases, however, this can cause a wrong-length record error to occur. // DLBL DISK,'MASTER',,SD,BLKSZ=OPT Create a SYSLST disk file when SYSLST is program-defined as a printer. Note that the SYSLST file is created on disk with a block size of 1210 bytes and the file name FISYSLS is used. The SYS001 assignment overrides the use of SYSLST. Chapter 6: Controlling File Independence 6–25
- 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 and 302: Changing File Characteristics Befor
- Page 303 and 304: Changing File Characteristics SRTCO
- Page 305 and 306: Changing File Characteristics Consi
- Page 307: Changing File Characteristics old b
- 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
- Page 352 and 353: Data Set Maintenance Disk User Owne
- Page 354 and 355: Data Set Maintenance • Entering D
- Page 356 and 357: Data Set Maintenance 03WE for tape
Changing File Characteristics<br />
The input tape file is FISYSIN and the output tape file is FISYSLS. The output<br />
file generated is a standard labeled tape. Logical unit SYS001 is used <strong>for</strong> the<br />
SYSIN file and SYS002 <strong>for</strong> the SYSLST file.<br />
// JOB TEST1<br />
// TLBL FISYSIN,'<strong>CA</strong>RD-INPUT',,SYS001<br />
// TLBL FISYSLS,'PRINT-OUTPUT',,SYS002,FIOPT=(SL)<br />
// ASSGN SYS001,TAPE<br />
// ASSGN SYS002,TAPE<br />
// EXEC COBTEST,SIZE=100K<br />
The file name is derived from:<br />
• DTFname in Assembler programs<br />
• File SELECT in COBOL programs.<br />
By default, the logical unit name is used.<br />
Example<br />
// DLBL SYS001, ...<br />
Recalculate the block size of an output disk file. Note that the block size of the<br />
disk file is calculated based upon the OPTBLKS value defined in the DYNAM/FI<br />
option record at installation time. For fixed-length records, the block size value<br />
is always a multiple of the record size value specified.<br />
// DLBL OUTPUT,'DISK-FILE',,SD,BLKSZ=OPT<br />
Reblock a tape file and set the options. The file below is reblocked on a tape to<br />
8000 bytes, and double buffering is specified (DB). In addition, a rewind and<br />
unload operation is per<strong>for</strong>med on the tape when it is closed (RUN).<br />
// TLBL OUTPUT,'TAPE-FILE',,BLKSZ=8000,FIOPT=(RUN,DB)<br />
Create a tape file and change the logical unit. Logical unit SYS018 is used to<br />
override the logical unit specified in the user's program.<br />
// TLBL TAPDISK,'TAPE-DISK',,SYS018<br />
Read a disk file created with reblocked size. Note that if the block size operand<br />
were omitted, the block size value would default to the one in the user's<br />
program. In many cases, however, this can cause a wrong-length record error<br />
to occur.<br />
// DLBL DISK,'MASTER',,SD,BLKSZ=OPT<br />
Create a SYSLST disk file when SYSLST is program-defined as a printer. Note<br />
that the SYSLST file is created on disk with a block size of 1210 bytes and the<br />
file name FISYSLS is used. The SYS001 assignment overrides the use of<br />
SYSLST.<br />
Chapter 6: Controlling File Independence 6–25