Hi Lizette,
I misspoke. You're right.

Regards,
David

On 2019-08-25 10:04, Lizette Koehler wrote:
> David
>
> I think RETRY(YES) is to recover from space abends.
>
> >From the manual
>
> RETRY
>      indicates whether SMP/E should try to recover from out-of-space errors 
> for utilities it calls.
>
>      YES
>          indicates that SMP/E should try to recover and retry the utility if 
> a RETRYDDN list is available in the OPTIONS entry that is in effect. 
> RETRY(YES) is the default.
>
>          If retry processing does not reclaim sufficient space and input to 
> the utility was batched (copy or link-edit utility only), SMP/E debatches the 
> input and retries the utility for each member separately. If this final 
> attempt fails, the resulting x37 abend is treated as an unacceptable utility 
> return code. In this case, processing continues for SYSMODs containing 
> eligible updates to other libraries, but processing fails for SYSMODs 
> containing unprocessed elements for the out-of-space library (and it fails 
> for any SYSMODs that are dependent on the failed SYSMODs). For guidance on 
> setting up the desired retry processing, see SMP/E for z/OS User's Guide. For 
> more information about OPTIONS entries, see SMP/E for z/OS Reference.
>
>          If there is no RETRYDDN list, SMP/E does not try to recover from 
> out-of-space errors, even if you specify YES.
>      NO
>          indicates that SMP/E should not try to recover from the error.
>
>
> Lizette
>
>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
>> David Spiegel
>> Sent: Sunday, August 25, 2019 7:01 AM
>> To: [email protected]
>> Subject: Re: GIM38201E and GIM31901I
>>
>> Hi Peter,
>> Remove the RETRY(YES).
>> This will stop SMP/e from APPLYing "old" PTFs.
>>
>> Regards,
>> David
>>
>> On 2019-08-25 09:53, Peter wrote:
>>> Here is the control statement :
>>>
>>> SMPCNTL DD *
>>> SET BDY TZONE .
>>> APPLY CHECK
>>> GROUPEXTEND
>>> BYPASS((HOLDSYSTEM))
>>> RETRY(YES)
>>> .
>>>
>>>
>>> On Sun, 25 Aug, 2019, 4:30 PM David Spiegel, <[email protected]>
>>> wrote:
>>>
>>>> Hi Peter,
>>>> - Modifying vendor-supplied MCS is NEVER a good idea.
>>>> - The messages means that you are trying to APPLY a lower-level PTF
>>>> than is currently APPLYd.
>>>> (Do you really want to back-level your software?) It would be helpful
>>>> to supply your entire //SMPCNTL when asking questions of this nature.
>>>> That is, there is not enough context to decipher what you're attempting.
>>>>
>>>> Regards,
>>>> David
>>>>
>>>> On 2019-08-25 03:21, Peter wrote:
>>>>> Hi
>>>>>
>>>>> I am apply RSU for our zOS system. I am receiving a error message
>>>>>
>>>>> GIM38201E ** THERE IS A MODID ERROR FOR MOD ENTRY EZBTCRDF IN SYSMOD
>>>> UI34556
>>>>> GIM31901I SYSMOD UI34556 DOES NOT SPECIFY UI46897 ON PRE OR SUP OPERAND.
>>>>> UI46897 IS THE RMID FOR MOD EZBTCRDF THAT IS CURRENTLY INSTALLED.
>>>>>
>>>>> GIM22601I  APPLY PROCESSING FAILED FOR SYSMOD UI34556.
>>>>>
>>>>> Does it mean the PTF UI46897 applied should be restored and modify
>>>>> its
>>>> MCS
>>>>> to add UI34556 as its PRE ?
>>>>>
>>>>> Is my understanding correct?
>>>>>
>>>>> Could someone please shed light on ?
>>>>>
>>>>> zOS 2.2
>>>>>
>>>>> Peter
>>>>>
>>>>> --------------------------------------------------------------------
>>>>> -- 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
> .
>


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

Reply via email to