> On Dec 20, 2017, at 7:25 PM, CM Poncelet <[email protected]> wrote: > >>> From a recent thread (rant?) in ASSEMBLER-LIST: >> >> ... Do you stand by "SVC 99 for good measure"? Generally, products >> do not implement it for good reason. Irrelevant in CICS and IMS. >> In batch, it bypasses job scheduler, job restart, violates production >> control requirements, bypasses JES3 resource management >> and potentially poses a production security risk. TSO has the >> alloc command which can easily be used in clists. It exists >> because of MVS UNIX. ... >> >> Disregard the anachronism in the last sentence. If, hypothetically, >> DYNALLOC except by initiator is so harmful as to be prohibited in >> production jobs, is there any way to do so? If it were possible, >> what would be the collateral damage? What fraction of production >> jobs would work, unmodified, without using DYNALLOC? >> >> Are code reviews a better technique? Other (specify)? >> >> — gil
Gil, I won’t go into the details as I am not sure I know all of them. We had a fairly large CICS system of at least 1400 users. One of the illustrious consultants got involved in a data center issue and decided to bypass the DC issue by attaching the OCR document reader from CICS and read the OCR documents directly. We had no real idea that this was going on. This was also during our trials and tribulation with the infamous (to us) enque problem. I get a call saying that CICS is having an issue and that I should investigate. I am sitting at the system console and the operators get a phone call to tell the OCR people to ready the machine. The console operator did so at this point I ask the operator who it is and its a clerk from 10 floors away. I asked for the phone and told the person who I was and asked what was going on. That is when I found out about the use of dynamic allocation in CICS. I went down to the bosses office and told him what was going on and he was reasonably technical and saw the implications for our other allocation issues. He gets all the info I have and goes up to our VP and tells him what is going on and if CICS gets hung up because of Q4 issues we can’t be blamed. He says yes this is a delicate issue and says he will discuss it with the group VP. After a few days he tells us that they are willing to take the hit and not to worry. As I have said before we had *MAJOR* Q4 issues. One of the dumps I looked at before giving it to IBM there was a trail of 200 asid’s waiting and the VP of the programming group complained to our VP about the issue and our VP said to him, we warned you, this outage is not all yours but if you didn’t do the OCR unit allocation you wouldn’t have this issue. Ed ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
