We have CAVIEW on the mainframe, sequential files containing report data are sent to CAVIEW via the mainframe utility IEBGENER at the ends of jobs that produce reports. This system DID have straight JCL - we converted to JCL-and-cataloged PROCEDURE (PROC). The filename into CAVIEW, the CAVIEW reference for SYSUT2
remained the same (e.g.
//SYSUT2 DD SYSOUT=(0,TOTRPT1M) )
the JOBNAME remained the same and the stepname within the PROC remained the same.
So we thought there would be no problem with CAVIEW. However apparently the fact that there is now (by default) a PROCSTEPNAME caused issue, and we had to re-request access for all users - our CAVIEW person had to resetup everything. My 1st question is: What REALLY caused the issue here? Is it really just that we now have a PROC? My 2nd question has to do with the fact that we have more JCL to convert to JCL-and-PROC. Is there any way I can "tweak" the JCL and/or PROC so CAVIEW will work without issue? Or do we have to re-request access and resetup everything - THIS TIME in advance of going to production with the changes!!!!!
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!