Hi Dean,
z/XDC's "LOAD" command loads a module into
storage according to the same default rules that
all other processes would follow, and then it
produces a two part report from which you can
discern which instance got LOAD'd to you (when multiple instances exist).
Example. Suppose I issue "LOAD XXX". The report would look something like this:
ENTRY PRIMARY REFRNCE USE
SUB- ATTRIBUTES
SEQ# NAME NAME TCB/RB# COUNT
ASID ENTRY ADDRESS KEY POOL (ATTR ATTR2 ATTR3-ATTRB)
_ 1 XXX 5 LLE 1-1 COMN
00000000_0099B070 0s DLPA B12204-10 RENT REUS CDE APFLIB CDX DLPA NIP
ENTRY PRIMARY DFINING USE
SUB- ATTRIBUTES
SEQ# NAME NAME QUEUE COUNT
ASID ENTRY ADDRESS KEY POOL (ATTR ATTR2 ATTR3-ATTRB)
_ 3 XXX LPQ 4 COMN
00000000_0099B070 0s DLPA B12204-10 RENT REUS CDE APFLIB CDX DLPA NIP
_ 4 XXX PLPA COMN
00000000_00C71070 0s PLPA B12200-18 RENT REUS LPDE APFLIB CDX NIP
The first part reports who the users are of the
module within your address space. In this case:
* There is only one user.
* It is task #5 (because that's where XDC was
running when you told it to "LOAD XXX").
The second part reports all instances of the load
module that exist in your address space. In this case:
* There are two instances.
* The first instance overrides the second.
* The first instance is in the [Dynamic] Link
Pack Area. It was probably created by a "SETPROG
LPA,ADD" Operator command to replace the original
PLPA instance with a newer one.
* The second instance exists in the PLPA.
This was the "original" instance created at IPL
time. It is dormant because all attempts to
LINK/LOAD/ATTACH XXX will never reach this second
instance because they will be satisfied by the first.
From the first report, you can tell that the
z/XDC "LOAD" command gave you access to the first
(newer) instance. You can tell this by looking at "ENTRY ADDRESS" field.
After issuing the "LOAD" command, you can then
use z/XDC's "FORMAT" command to look at the
module's content. Example: "FORMAT XXX+43C" will
show you what's at +43C past XXX's entry point.
IHTH,
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: <mailto:[email protected]>[email protected]
Home page: www.colesoft.com
LinkedIn: www.xdc.com
Facebook: www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware
Tools: <http://www.colesoft.com/zxdc/>z/XDC for Assembler debugging
<http://www.colesoft.com/c/>c<http://www.colesoft.com/c/>/XDC
for C debugging
At 3/5/2020 10:10 AM, Nai, Dean wrote:
Hi Chris,
Let me check XDC..thanks
Dean
On 3/5/20, 9:59 AM, "IBM Mainframe Discussion
List on behalf of Chris Parker"
<[email protected] on behalf of [email protected]> wrote:
> EXTERNAL: Do not open attachments or click
on links unless you recognize and trust the sender.
>
>Hi Dean,
>
>I donât know what type of tooling you
have. So, I'm not sure exactly what to
suggest. If you have an eyecatcher in the
module that you can verify, you could use the
tso test or testauth command specifying the
load module as the entry program and then just
dump the location and header. You could also
write a quick and dirty ASM program to do the load and dump the address.
>
>I have XDC. So, I would just start up a
session and issue a load command. :)
>
>Chris
>
>-----Original Message-----
>From: IBM Mainframe Discussion List
<[email protected]> On Behalf Of Nai, Dean
>Sent: Thursday, March 5, 2020 8:54 AM
>To: [email protected]
>Subject: Re: load modules
>
>Hi Larre,
> No luck. Iâm thinking this is something
that canât be found. Thanks for the response.
>
>Dean Nai
>Senior z/OS Systems Programmer
>Technical Services Group
>Department of Information Technology
>State of New Hampshire
>27 Hazen Drive
>Concord, NH 03301
> work: 603-271-1529
>
>
>
>On 3/5/20, 9:37 AM, "IBM Mainframe
Discussion List on behalf of Larre Shiller"
<[email protected] on behalf of
[email protected]> wrote:
>
>> EXTERNAL: Do not open attachments or
click on links unless you recognize and trust the sender.
>>
>>Dean -
>>
>>...how about using the TSO ISRDDN command
followed by LOAD module_name ...?
>>
>>Larre Shiller
>>US Social Security Administration
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
