I agree with Dave completely.  I do similar - on both APPLY CHECK and APPLY.  
Why spend an inordinate amount of time telling SMP/E manually to do what SMP/E 
is designed to do automatically.  Let it skip the open APARs and other things 
that will cause a "bad" return code.  Like Dave said, just verify that the 
things that caused the RC=8 are OK.  The CAUSER report is your friend here.  

Rex

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Jousma, David
Sent: Monday, June 22, 2020 6:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: SMP/e maintenance methodologies

I do not attempt to get a RC0 or RC4 apply.  What goes on goes on.  Obviously 
review results to make sure that there wasn't an issue, but coding up a bunch 
of excludes to not select those with holderror just to get a RC0 is not 
necessary in my opinion.

Here is one apply example

APPLY CHECK                         
       SOURCEID (                   
                  SYSPLXDS          
                  XSYSTEM           
                  HIPER             
                  IBM.*             
                  RSU*              
                  SECINT            
                  )                 
        GROUPEXTEND                 
            (                       
             NOAPARS                
             NOUSERMODS             
            )                       
        BYPASS   ( HOLDSYSTEM)      
        NOJCLINREPORT               
        RETRY    ( YES )            
        .                           

_____________________________________________________________________________________________________
Dave Jousma
AVP | Manager, Systems Engineering  

Fifth Third Bank  |  1830 East Paris Ave, SE  |  MD RSCB2H  |  Grand Rapids, MI 
49546
616.653.8429  |  fax: 616.653.2717


-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Edgington, Jerry
Sent: Monday, June 22, 2020 7:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SMP/e maintenance methodologies

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

Hello everyone,

I am looking for SMP/e methodologies about a couple of situations within SMP/e. 
 Just looking for how people do SMP/e maintenance in certain situations.

1)      What methodology is employed to get to a clean Apply Check, when you 
outstanding Error Holds? APARs without PTFs, local fix or work arounds?
2)      For Apply check, what PARMs do you use?  Select, FixCat, Bypass, etc?

I was taught a SMP/e methodology, many years ago, but just wondering if there 
might be a better way.

Thanks,
Jerry Edgington


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL 
EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**


This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to