Hi, I did a couple of tests.
If the VSAM is allocated to CICS I receive a IDC3351I with reason 168 during the VERIFY. As far as I understand, ALTER with no parm does nothing but ensure the file is not allocated to any other user. Hope this helps. Max <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Privo di virus.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> Il giorno mar 23 apr 2024 alle ore 15:51 Radoslaw Skorupka < [email protected]> ha scritto: > I have found a job with series of following commands: > ALTER HLQ.SOME.VSAM.CLSTR > ALTER HLQ.SOME.VSAM.CLSTR.* > ALTER HLQ.YET.ANOTHER > ALTER HLQ.YET.ANOTHER.* > ... > > Q: what does it do? > > > > Another question: > First step in the job is a series of VERIFY HLQ.SOME.VSAM commands. > During the day the VSAM files are in use by some CICS region. > Would the job harm CICS processing or just end with "dataset in use" > reason? > > -- > Radoslaw Skorupka > Lodz, Poland > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
