The real apply when doing a bypass holdsys does not get a zero return code but a 4.
________________________________ From: Scott Rowe <[email protected]> To: [email protected] Sent: Tue, April 5, 2011 3:04:18 PM Subject: Re: SMP/E BYPASS( HOLDSYS( <reason-list> ) ) I too use the generic HOLDSYS, and since I run APPLY CHECKS first, and review the hold listing, I see (and review) every hold that I'm bypassing before I do the real APPLY. On Mon, Apr 4, 2011 at 6:25 PM, Skip Robinson <[email protected]>wrote: > I always use the vanilla HOLDSYS with no qualifications. On the other > hand, I'm comfortable with letting sysmods fail for 'obvious' reasons like > missing co-reqs that are not yet available. RC 8 is not scary if you can > see in the CAUSER report that life will go on for now. Frankly, I'm > suspicious of a sizable APPLY that gets RC 0. Something must be getting > overlooked. ;-) > > . > . > JO.Skip Robinson > SCE Infrastructure Technology Services > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] > > > > From: Paul Gilmartin <[email protected]> > To: [email protected] > Date: 04/04/2011 03:08 PM > Subject: SMP/E BYPASS( HOLDSYS( <reason-list> ) ) > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > Why do programmers use "BYPASS( HOLDSYS( <reason-list> ) )" > rather than merely BYPASS( HOLDSYSTEM )? Are there some > reason codes to which they particularly want to be alerted > while others can be routinely bypassed by appearing in the > list? > > What's the process? Perhaps first: > > APPLY CHECK BYPASS( HOLDSYS( <ordinary-reasons> ) ) ..., > then resolve the unusual reason codes (GIM35965I) and do > APPLY BYPASS( HOLDSYSTEM ) ...? > > (Just wondering what we should supply in our JCL samples.) > > (In internal testing of PTFs, I'm inclined to supply a list > to detect typos in ++HOLD SYSTEM REASON( bogus ) ... MCS.) > > Thanks, > gil > > > ---------------------------------------------------------------------- > 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 > CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. 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 ---------------------------------------------------------------------- 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
