Hello I hope some of you can help me with this... We made a commitment to our user and applications teams that there would be no JCL changes required when we cut over to a new tape infrastructure. Our thinking was that we would virtualize everything. We are using STK VSM4's and 9940 backend. During this round of applications testing we ran into some issues. It seems that since we are including 3590 native tapes to go to the virtual, they may have to code vol=(,,,99) in their JCL. They have vol= in some of their JCL already so if we tried to go to a dataclass instead they would still have to make jcl changes. We also received a 937 on a job after a dataset went over 42 volumes here is what was indicated with the rc=40.
RACF definitions are inconsistent. A previously allocated multi-volume DASD data set or a tape volume is being processed for output. The current volume being processed at end of volume is defined to RACF, but not as part of the same volume set as the previous volume. The maximum number of volumes any dataset on the tape can span is 42. any suggestions would be greatly appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
