Yes. I do agree that in my z/OS 2.1 system  @@CBL2C with an
alias of EDCCBL2C  but in my z/OS 1.13 and other system is part of EDC4$006
and it is RF RN RU. But I am not able to understand how this is causing
this problem and is there any way to solve before I take further step to
raise PMR.



On Sat, Sep 6, 2014 at 5:17 PM, Mainframe Mainframe <[email protected]
> wrote:

> In distribution Library...
>
> ZOS21D.AEDCMOD1
>
> @@CBL2C                 EDC4$006    RF RN RU
> EDC@@248                EDC4$09E    RF RN RU
> EDC4$09D                            RF RN RU
>
>
> In my Target library, EDC@@248 is a module or not an alias of another
> module.
> EDC@@248                               RN RU
>
>
>
>
>
> On Sat, Sep 6, 2014 at 1:24 AM, Ed Gould <[email protected]> wrote:
>
>> On Sep 5, 2014, at 9:01 AM, Tom Marchant wrote:
>>
>>> -----------------SNIP------------------------
>>>>
>>>
>>> Not refreshable. That's what the Binder told you. You need to find out
>>> why.
>>> You may need to contact IBM.
>>>
>>>
>> Tom,
>>
>> I agree. the module somehow got linked incorrectly either from the last
>> PTF that hit it or it got linked outside of SMPE.
>> What the author should do is look at what the last PTF that hit the
>> module and see what the link parms were. There may have been a PTF that did
>> it by mistake and no ones caught it untillthe PTF that was going on was
>> "caught". In either case make sure through SMPE what the last PTF went on
>> and look at retain to see if it was in error and do the research on
>> previous PTF's to see eho caused the problem and open a PMR if everything
>> is Kosher.
>>
>> Ed
>>
>>
>> ----------------------------------------------------------------------
>> 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