Our apply of UI18451 got a binder RC of zero.
AMBLIST of STRXFRM is somewhat different, both it and EDS@@248 are aliases of
EDC4$09E:
LISTLOAD DDN=DD1,MEMBER=STRXFRM,OUTPUT=XREF
***** M O D U L E S U M M A R Y *****
MEMBER NAME: EDC4$09E
MAIN ENTRY POINT: 00000000
LIBRARY: DD1 (<-- i.e. SYS1.SCEELKED Ant.)
AMODE OF MAIN ENTRY POINT: 31
** ALIASES ** ENTRY POINT AMODE
EDC@@248 00000000 31
** STRXFRM 00000000 31
-----------------------------------------------------------------------------------------------------------------------
**** ATTRIBUTES OF MODULE ****
** BIT STATUS BIT STATUS BIT STATUS
BIT STATUS **
0 RENT 1 REUS 2 NOT-OVLY
3 NOT-TEST
4 NOT-OL 5 BLOCK 6 EXEC
7 1-TXT
8 NOT-DC 9 ZERO-ORG 10 EP-ZERO
11 NO-RLD
12 EDIT 13 NO-SYMS 14 F-LEVEL
15 REFR
-----------------------------------------------------------------------------------------------------------------------
MODULE SSI: NONE
APFCODE: 00000000
RMODE: ANY
LONGPARM: NO
*****LOAD MODULE PROCESSED EITHER BY VS LINKAGE EDITOR OR
BINDER
NUMERICAL MAP AND CROSS-REFERENCE LIST OF LOAD
MODULE EDC4$09E PAGE 0001
CONTROL SECTION ENTRY
LMOD LOC NAME LENGTH TYPE LMOD
LOC CSECT LOC NAME
00 STRXFRM 0A SD
LENGTH OF LOAD MODULE 10
ALPHABETICAL MAP OF LOAD MODULE EDC4$09E
PAGE 0002
CONTROL SECTION ENTRY
NAME LMOD LOC LENGTH TYPE NAME
LMOD LOC CSECT LOC CSECT NAME
STRXFRM 00 0A SD
** END OF MAP AND CROSS-REFERENCE LISTING
Only z/OS 2.1 here, no prior z/OS to compare it to.
Ant.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Mainframe Mainframe
Sent: Friday, 5 September 2014 1:19 PM
To: [email protected]
Subject: Re: RSU APPLY ISSUE GIM23911E
Below Output,
LISTLOAD DDN=SCEELKED,MEMBER=STRXFRM,OUTPUT=XREF
00060001
***** M O D U L E S U M M A R Y *****
MEMBER NAME: EDC@@248
LIBRARY: SCEELKED
** ALIASES ** ENTRY POINT AMODE
** STRXFRM 00000000 31
--------------------------------------------------------------------------------
**** ATTRIBUTES OF MODULE ****
** BIT STATUS BIT STATUS BIT STATUS
0 RENT 1 REUS 2 NOT-OVLY
4 NOT-OL 5 BLOCK 6 EXEC
8 NOT-DC 9 ZERO-ORG 10 EP-ZERO
12 EDIT 13 NO-SYMS 14 F-LEVEL
--------------------------------------------------------------------------------
MODULE SSI: NONE
APFCODE: 00000000
RMODE: ANY
LONGPARM: NO
*****LOAD MODULE PROCESSED EITHER BY VS LINKAGE EDITOR OR BIN
NUMERICAL MAP AND CROSS-REFERENCE LIST OF LOAD MODU
CONTROL SECTION
ENTRY
LMOD LOC NAME LENGTH TYPE
LMOD LO
00 STRXFRM 0A SD
LENGTH OF LOAD MODULE 10
ALPHABETICAL MAP OF LOAD MODULE EDC@
@248
CONTROL SECTION ENTRY
NAME LMOD LOC LENGTH TYPE NAME
LMO
STRXFRM 00 0A SD
** END OF MAP AND CROSS-REFERENCE LISTING
******************************** BOTTOM OF DATA
********************************
On Fri, Sep 5, 2014 at 9:18 AM, Mainframe Mainframe <[email protected]
> wrote:
> Below O/P for AMBLIST
>
>
>
>
> On Fri, Sep 5, 2014 at 1:10 AM, Doug Henry <[email protected]> wrote:
>
>> On Thu, 4 Sep 2014 19:23:25 +0000, Gibney, Dave <[email protected]> wrote:
>>
>> >I could be way off base, but given that the OP just finished a
>> >thread
>> where the solution was a mass/conditional zoneedit of his >DDDEFs, I
>> would look very closely at which libraries are actually being used
>> and updated by this SMP/E running. An inadvertent >mixing of LE levels is
>> scary.
>>
>> Hi Dave,
>> Yes this might very well be the issue. Just concentrating on the
>> first module that causes the problem, I suggest that OP do an amblist
>> and send the output to the list. This output should have rent (bit
>> 0), reuse (bit 1), and refr (bit 15) set.
>>
>> //LIST EXEC PGM=AMBLIST
>> //SYSPRINT DD SYSOUT=*
>> //SCEELKED DD DSN=SYS1.SCEELKED,DISP=SHR
>> //SYSIN DD *
>> LISTLOAD DDN=SCEELKED,MEMBER=STRXFRM,OUTPUT=XREF
>> /*
>>
>> Doug
>>
>> ---------------------------------------------------------------------
>> - 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
