[Note: Jay and I work on the same team; he joined us earlier this year.] On Aug 5, 2025, at 4:22 AM, Dejan Stamatovic <[email protected]> wrote:
Hi Jay, Unit=VIO is not mandatory on a z/OS system. If you like to use it so much, you can reintroduce it for the sake of old JCL. I have seen many customers replace this by using DFSMS ACS routines and directing unit=VIO to temporary data sets allocation usually using a separate DFSMS Storage group. unit=VIO is anyway not to be used for allocation of DFSORT temporary data sets so if you stop using it, this might even simplify your z/OS environment by not using an additional esoteric name. This is up to you. In fact, “The SMS ACS routines will redirect it to VIO if you just leave the UNIT out” was my initial response. The problem is Jay is installing a vendor product that has “UNIT(VIO)” hard coded in a call to BPXWDYN. To which my response was, “do they know it’s the 21st century now?” -- Curtis Pew, Mainframe Specialist The University of Texas at Austin | ET Campus Solutions ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
