I think I'm getting close to being able to generate the UCLIN from
ADATA. I've decided the my job to add a the exit as a usermod should
start with an assembly anyway, no real point in going further if that
fails :)

  I have sort pulling ADATA type x'0062' records, but it looks like I
need to move to REXX to deal with the variable length macro names in the
ADATA records. I also have considered parsing the assembler listing, but
that would be prone to failure as they change HLASM. I would hope ADATA
to remain more stable.

  I'll be glad to share what I come up with when I get there.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Brian Peterson
Sent: Wednesday, September 10, 2008 4:14 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SMP/E GIM44402W

To perhaps more completely answer this question....

FIRST, you must make sure your usermod is a valid and complete SMP/E 
entity.  Here's an example from my shop:

++USERMOD(HASPUEX)  REWORK(2008159).                  
++VER (Z038) FMID(HJE7740).                           
++JCLIN.                                              
//LINK0002 EXEC PGM=IEWBLINK,PARM=('OPTIONS(GENOPTS)')
//GENOPTS  DD *                                       
                  RENT,REUS,REFR,NCAL                 
//SYSLMOD  DD DSN=SYS1.SHASLNKE                       
//SYSLIN   DD *                                       
 INCLUDE AHASMOD(HASPUEX)                             
 NAME  HASPUEX                                        
++SRC  (HASPUEX) SYSLIB(SHASSRC) DISTLIB(AHASSRC) .   
(assembler source code here)

In this case, my usermod HASPUEX creates SRC and MOD entries for module 
HASPUEX.  If I have used UCLIN to create a GENASM entry for MAC $PDDB 
which lists HASPUEX, then if an IBM PTF comes along which updates $PDDB,

SMP/E will look for a SRC entry called HASPUEX and will attempt to
assemble 
it.  Because my usermod is complete in SMP/E, SMP/E will be successful
when 
it assembles HASPUEX and will place the module in the correct load
library.

Creating the list of macros for the UCLIN step is a completely manual
process - 
I don't know a way to automatically do this and skip the UCLIN step.  I
would 
be interested in hearing if someone else has a better idea!

Hope these ideas help you.

Brian


On Wed, 10 Sep 2008 17:44:38 -0500, Brian Peterson wrote:

>I believe the only way this is done is to run UCLIN.  The idea is to
update 
each
>JES2 macro that your JES2 exit uses, such as $PDDB, to add a GENASM
entry
>pointing to your JES2 user exit SRC name.  That way, SMP/E knows that
>whenever $PDDB (as an example) is updated, it will cause a re-assembly
of
>every program listed in the GENASM entry for $PDDB.
>
>An example of how this is done can be found in SYS1.SISFJCL(ISFISUCL),
>which is a sample job provided by SDSF to update JES2 macros to
>automatically reassmble affected SDSF modules.  You would do something
>similar for your JES2 usermods, and just rerun the UCLIN each time you
install
>a new z/OS release.
>
>Brian
>
>On Wed, 10 Sep 2008 15:33:35 -0700, Gibney, Dave wrote:
>
>>   For several iterations now, (1.7 to 1.9 this time) I've tried to
>>package my JES2 exits as usermods and have wanted SMP/E to notify (or
>>really, just reassemble/link) when a PTF effects them. But all I ever
>>get is:
>>
>>GIM44402W    ZJ01USEP WAS NOT ASSEMBLED FOR MAC $PDDB IN SYSMOD
>UA38779
>>BECAUSE
>>             THERE IS NO MOD ENTRY FOR ZJ01USEP. SMP/E CANNOT
>DETERMINE
>>THE
>>             TARGET LIBRARY FOR THE ASSEMBLER OUTPUT.
>>
>>
>>Which does draw my attention, but isn't what I was hoping for.
>>
>>   Also, I just tried one where I included the entire source in IEV90
>>JCLIN and then again after a ++SRC. It found few of the macros
>>referenced as most are pulled in by $MODULE. I'm starting to look at
>>ADATA to see if I can pull from there a useful input to the JCLIN.
>>
>>   Time pressures are about to push me back to just shoving my exits
>>into a local linklst library and being done with it again, but I'd
>>really like to find out what I'm missing with my understanding of
SMP/E.
>>
>>   Sorry to become to recently verbose/whining on IBM-MAIN :), but I'd
>>be grateful for any help.
>>
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
>Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to