Re: ICSF EXIT
Angel-Luis Dominguez
Manuals along all the releases only say:
"The installation exit gets passed the address of the service parameter list
in Register 1."
But I have encountered that ......
If you have HCR7740 function, the parameter list addressed by R1 is in
the ASID of ICSF.
But if you migrate to HCR7750 function, the exits that are working fine
starts to have S0C4 abend's and others, even you have ptf's arising this
applied..
That is due to the list pointed by R1 isn't in ICSF ASID and is now in the
ASID of the user requiring ICSF services.
I haven't found any documentation of this change and I needed serveral
days to detect the change thinking it was a problem of my code instead a
change in funcionality.
Apar OA23636 points to this but was applied. The key for resolving was
in a comment in apar OA23955. Thats it's the text of the comment:
"I have added a " LAM AR1,AR1,=F'1' " instruction near the start of the
User Service Routine and this has corrected the abend"
Angel Luis Dom�nguez
z/os sysprog
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Walt Farrell
<angel_luis_do...@YAHOO.ES> wrote:
>I am developping ICSF service exits to write information in SMF.
>
>Manuals along all the releases only say:
>
>"The installation exit gets passed the address of the service parameter list
>in Register 1."
>
>But I have encountered that ......
>
>If you have HCR7740 function, the parameter list addressed by R1 is in
>the ASID of ICSF.
>
>But if you migrate to HCR7750 function, the exits that are working fine
>starts to have S0C4 abend's and others, even you have ptf's arising this
>applied..
>
>That is due to the list pointed by R1 isn't in ICSF ASID and is now in the
>ASID of the user requiring ICSF services.
>
>I haven't found any documentation of this change and I needed serveral
>days to detect the change thinking it was a problem of my code instead a
>change in funcionality.
>
>Apar OA23636 points to this but was applied. The key for resolving was
>in a comment in apar OA23955. Thats it's the text of the comment:
>
>"I have added a " LAM AR1,AR1,=F'1' " instruction near the start of the
>User Service Routine and this has corrected the abend"
The book for z/OS V1 R11 (ICSF FMID HCR7770, see
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CSFB2ZA0/5.3.2?SHELF=EZ2ZBK0H&DT=20091114130346
or http://preview.tinyurl.com/yeb9hnf ) and as I read it the book clearly
states that the service exits run in cross-memory mode and must specify an
ALET of 1 to access the parameters, which will be in the secondary address
space. That same text is in the ICSF books at least as far back as z/OS V1 R7.
APAR OA23636 addresses an error in Omegamon/XE where the exits it provides
were not properly using the ALET of 1, and via that APAR they corrected
their exits to provide that ALET.
--
Walt
Angel-Luis Dominguez
>> The book for z/OS V1 R11 (ICSF FMID HCR7770,
>> see /publibz.boulder.ibm.com/cgi-
>> bin/bookmgr_OS390/BOOKS/CSFB2ZA0/5.3.2?
>> SHELF=EZ2ZBK0H&DT=20091114130346
>> or http://preview.tinyurl.com/yeb9hnf ) and as I read it the book clearly
>> states that
>> the service exits run in cross-memory mode and must specify an ALET of 1
>> 1 to access the parameters, which will be in the secondary address space
>> That same text is in the ICSF books at least as far back as z/OS V1 R7
That you said is correct, you need to be in cross memory mode to access the
parameters.... to get the VALUE of each parameter.
The problem is in THE LIST OF PARAMETERS ADDRESSES.
In HCR7740 you MUST take the addr. of each parameter in primary mode, then
switch to secondary to obtain it's value. My first code works properly from
time and it is working now in the sysplexes running HCR7740.
But after migrating to HCR7750, recompiling code ins't sufficient.
The list of parameters addresses ISN'T IN THE PRIMARY, you must change to
the secondary to access the list then obtain values.
I think the change is significative. I was unable to find documentation about
this, nor in the books nor in the PTF's, and need a lot of tests and a piece of
luck to discover this change.
It was mi experience in these days and write it here for general knowledge in
case anybody could experience this.
Regards
Angel Luis Dom�nguez
z/os sysprog
----------------------------------------------------------------------