At month end a job of ours that nornally runs a few minutes took several hours by lpar saturation. Our job reads a JCL PDS used by the DBAs. They complained because their job and subsequent jobs were held up by hours. And once their job ran it took an hour instead of a minute (no exaggeration!).
We have been asked to change our job which would require changing it on at least 6 plexes. Our solution is for them to change their job. They are using a construct that has the followed DD //OUTPUT DD DISP=OLD, DSN=IMS.DBA.JCLLIB(MEMBER) The question I have is: Is the DISP=OLD needed or does the QSAM interface to BPAM handle collisions? I vaguely remember that the MIM product had a feature added to it to handle member collisions in the middle to late 1980's by Ed Legowski so collisions were an issue back then. (EDIF maybe????) So what is current state of the art? We are 1.10 with 1.11 rolling out this year (it's on 5-10 lpars already). ----------------------------------------- The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you ---------------------------------------------------------------------- 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
