We had an instance like the below..
A VSAM file which has got opened by a CICS program in a LPAR region needs to be copied to another LPAR region. We had given shroption (2,3) which doesnt allow us to proceed. As share option 2 allows only one processor at a time to open a data [...]
Archive for the ‘dataset’ Category
Assign separate name for temporary dataset
Posted in ISPF, JCL, MF TIPS, MVS, dataset, tagged dataset, dsn, Mainframe, temp dataset, temp dsn, temporary dataset on April 8, 2008 | Leave a Comment »
There are some mainframe jobs needs to be submitted in bulk mode. There is a requirement to put the jobname in the generated temp dataset name. They all use the exact same skeleton JCL, including the same DSN=&&SB250DD1 DD statement. This would be more helpful to avoid the ENQ conflicts
//GENER EXEC PGM=IEBUPDTE,PARM=NEW
//SYSPRINT DD DUMMY
//SYSUT2 [...]
Dataset control block
Posted in MVS, dataset, tagged block size, dataset, lrecl, Mainframe on April 7, 2008 | Leave a Comment »
The amount of virtual storage required to drive a physical I/O operation is totally dependent on access-method internal design, which is mostly outside our control. If the desired Key field and Data field just happen to be identical to the physical Count field (a pathological case), you could surely design a channel program that could [...]


