The sample I’ve provided was an actual RSU install. The exclude was PTF’s that 
needed to be excluded for various reasons. Most likely PTF’s in error. As for 
defaults that don’t need coded, who cares? Defaults are nice to show for people 
who aren’t privy to them. The other SMPWRK & SYSUT were most likely generated 
by SMP/e and meaningless to his question but I know how you like to show 
everyone your special intelligence. This example was from 2017 when I was 
installing & maintaining DB2. 


Sent from Yahoo Mail for iPhone


On Sunday, June 16, 2024, 12:27 AM, Brian Westerman 
<[email protected]> wrote:

I agree with everything except the last part about selecting the PTFs 
individually.  I do the same thing that the OP is doing.  My reason is that I 
can get the ones the "need" to be excluded from the applychk, but since he is 
doing a RSU, he likely wants everything that is not going to fail because of 
failed or missing prereqs.

Coding defaults never hurts though.

As far as getting through the 134 PTF's you pretty much have to look at them 
all and see if the action is going to need you to do something that you can't 
or don't want to do or will affect something poorly in your system.  It's 
difficult to tell you for sure without knowing anything about your site and if 
the required actions are going to present a problem for you.

If it helps, most of the actions are likely fairly benign things, but again, 
it's difficult to tell you without specific knowledge of the action items in 
question.  

Brian

On Sat, 15 Jun 2024 23:00:55 -0400, David Spiegel <[email protected]> 
wrote:

>Hi Dave,
>- RETRY(YES) and JCLINREPORT are defaults. There is no need to code them.
>- The SYSUTx ALLOCATIONS might be too small
>- The SMPWRKx Allocations could benefit from half-track blocking (i.e.
>BLKSIZE=27920).
>- Instead of PTFS and EXCLUDE, why not SELECT the 134 PTFs?
>
>Regards,
>David
>
>On 2024-06-14 18:30, Dave Beagle wrote:
>> Depends on the holds. DOC holds are easily bypassed. Others not entirely 
>> bypass-able.(although most are) Some of them you might have to perform a 
>> bind to finish the installation. Here is a sample.
>> //WJJCAPCK JOB (3200,TBL1),'APCK DB2 MAINT',CLASS=8,MSGCLASS=Q,
>> //         NOTIFY=&SYSUID,REGION=6M
>> /*JOBPARM SYSAFF=BCWD
>> //*
>> //S1       EXEC PGM=GIMSMP,
>> //         PARM='PROCESS=WAIT',
>> //         DYNAMNBR=120
>> //*
>> //* NOTE:      THIS JCL CREATED BY THE COMMAND GENERATION DIALOGS.
>> //*
>> //*            SMP ZONE-RELATED FILES ARE DYNAMICALLY ALLOCATED,
>> //*            THIS INCLUDES THE SMPPTS, SMPLOG, AND SMPTLIB DATA SETS,
>> //*            IF APPLICABLE.
>> //*
>> //* SMP FILES
>> //*
>> //SMPCSI   DD DISP=SHR,DSN=SMPE.DB2V8R1.GLOBAL.CSI
>> //SMPOUT   DD SYSOUT=*
>> //SMPRPT   DD SYSOUT=*
>> //SMPLIST  DD SYSOUT=*
>> //SYSPRINT DD SYSOUT=*
>> //*
>> //*      UTILITY WORK DATA SETS IF REQUIRED FOR THE COMMAND
>> //*      FOLLOW HERE.
>> //*      INFORMATION FOR THE ALLOCATION OF THESE DATASETS IS
>> //*      SET USING OPTION 0 (SETTINGS) FROM THE SMP/E PRIMARY
>> //*      OPTION PANEL.
>> //*
>> //SYSUT1   DD UNIT=SYSDA,SPACE=(3120,(380,760))
>> //SYSUT2   DD UNIT=SYSDA,SPACE=(3120,(380,760))
>> //SYSUT3   DD UNIT=SYSDA,SPACE=(3120,(380,760))
>> //SYSUT4   DD UNIT=SYSDA,SPACE=(3120,(38,100))
>> //*
>> //*      SMP TEMPORARY WORK DATA SETS
>> //*
>> //SMPWRK1  DD UNIT=SYSDA,
>> //            SPACE=(3120,(364,380,500)),
>> //            DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
>> //SMPWRK2  DD UNIT=SYSDA,
>> //            SPACE=(3120,(364,380,500)),
>> //            DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
>> //SMPWRK3  DD UNIT=SYSDA,
>> //            SPACE=(3120,(364,380,500)),
>> //            DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
>> //SMPWRK4  DD UNIT=SYSDA,
>> //            SPACE=(3120,(364,380,500)),
>> //            DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
>> //SMPWRK6  DD UNIT=SYSDA,
>> //            SPACE=(3120,(364,380,500)),
>> //            DCB=(RECFM=FB,BLKSIZE=3120)
>> //*
>> //*
>> //SMPCNTL  DD *
>>    SET    BOUNDARY (DSN8TRG)
>>                    .
>>    APPLY
>>           PTFS
>>           BYPASS   (
>>                     HOLDSYSTEM
>>                              (
>>                                DOC
>>                                DB2BIND
>>                                IPL
>>                                ACTION
>>                                AO
>>                                DEP
>>                                DELETE
>>                              )
>>                    )
>>           JCLINREPORT
>>           CHECK
>>           EXCLUDE  (
>>                     UK16725
>>                     UK16766
>>                     UK17549
>>                     UK17614
>>                     UK17616
>>                     UK17619
>>                     UK17786
>>                     UK17972
>>                     UK18140
>>                     UK18173
>>                     UK18509
>>                     UK18859
>>                     UK19013
>>                     UK19209
>>                     UK19249
>>                     UK19337
>>                     UK19345
>>                     UK19528
>>                     UK19578
>>                     UK19603
>>                     UK20093
>>                     UK20531
>>                     UK20550
>>                     UK20557
>>                     UK20696
>>                     UK21117
>>                    )
>>           GROUPEXTEND
>>           RETRY(YES)
>>                  .
>>
>> Dave
>>
>> Sent from Yahoo Mail for iPhone
>>
>>
>> On Friday, June 14, 2024, 9:19 AM, Steve Beaver 
>> <[email protected]> wrote:
>>
>> Upfront - I am not a DB2 SYSPROG, SYSADM, or Programmer
>>
>>
>>
>> I have pulled in and applied DB2 V12 RSU2403.  That was the easy part.
>>
>>
>>
>> There are 134 PTF's with HOLD ACTION and that is where  trouble is going to
>>
>> Begin.
>>
>>
>>
>> Does anyone have a Home Grown implementation document to help me get
>>
>> Through these 134 PTF's with HOLD.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Stev
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> 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
>
>----------------------------------------------------------------------
>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




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to