Author Topic: Cobol ARSUUPDZ and ODSXUPDZ dynamic exit - V9.5  (Read 141 times)

Nolan

  • Jr. Member
  • **
  • Posts: 56
    • View Profile
Cobol ARSUUPDZ and ODSXUPDZ dynamic exit - V9.5
« on: March 23, 2017, 07:57:33 AM »
Starting a new thread to get more visibility.   Thanks

I have been struggling to get this resolved and am hoping someone has been there and done that.

We are going from V9.0 to V9.5, using the ODSXUPDZ in V9.0 is working just fine with the ARS.RSADUPDT exit.

I compiled the ARSUUPDC using the supplied ARSUUPDJ JCL and deployed to the /bin/exits
I made minor changes to ARSUUPDC to display/debug some info and update a value to confirm it passes the updates out to the MVS exit RSA.ARSUUPDT.

ARSUUPDC - in OMVS

working storage
copy arsuupda.

call ARSZUXPL-MODFCNP using by reference ARSUUPDA
returning rc

My understanding is this call to ARSZUXPL-MODFCNP triggers the MVS exit RSA.ARSUUPDT


ODSXUPDZ - MVS

Linkage Section.

copy ARSUUPDA.

Procedure Division using
by reference ARSUUPDA.

The logging/debug of the MVS exit shows that the ARSUUPDA values are received and then updated successfully.

However the OMVS Exit ARSUUPDA logging/debug shows it doesn’t see the values modified by MVS exit.

In MVS – Display the results
Code
String ' ARSUUPDA-UPDATE = ' Pic-X8-2-98
' / X''' Pic-X200(1:8) ''''
delimited by size into SYSOUTZ-DATA.

Results
ARSUUPDA-UPDATE = 00000001 / X'00000001'

In OMVS
Display "UPDATE Value: " ARSUUPDA-UPDATE upon syspunch

Results
UPDATE Value: 000000000 UPDTEXIT

Is there some other step I need to turn on to ensure the values are read correctly in ARSUUPDC after ODSXUPDZ.

I will admit I am not an experienced COBOL programmer so if there is something you think might help, please suggest anything
J.

#zOS #AIX #Windows #Multiplatforms
#DB2 #TSM #ODF #zODF #ODWEK
#CapacityPlanning #AFP #ReportDistribution
#Finance

Nolan

  • Jr. Member
  • **
  • Posts: 56
    • View Profile
Re: Cobol ARSUUPDZ and ODSXUPDZ dynamic exit - V9.5
« Reply #1 on: July 26, 2017, 06:58:12 AM »
RESOLVED  :D

Details not included in the readme or anywhere else I looked.

To continue using the Report Specification Exit in COBOL with out modifications you must do the following steps.

1. Recompile the exit as per usual with any release
2. Create a directory in OMVS to hold customer exits.  Example: /usr/lpp/ars/V9R5M0/custom/exits
3. Update ars.cfg with path name of custom exits.  Example: ARS_USER_EXITS_DIR=/usr/lpp/ars/V9R5M0/custom/exits
4. Update and run SARSINST(ARSUUPDJ).  Ensure you point the hfs file to the same path used above.  Example:  /usr/lpp/ars/V9R5M0/custom/exits
     Note you do not need to modify SARSINST(ARSUUPDC)

WARNING.  You need to use your custom path for other exits.
For Security Exit we had to use two of the stock samples
SARSINST(ARSUSECX) - Customized for our needs
SARSINST(ARSUSEJJ) - Stock IBM SARSINST(ARSUSECC)
SARSINST(ARSUPERJ) - Stock IBM SARSINST(ARSUPERC) - required if using security exit apparently.

For Banner Exit
SARSINST(ARSCODFX) - Stock IBM SARSINST(ARSODFXA)
SARSINST(ARSCODFX)  - We Modified SARSINST(ARSODFXB) to our needs
SARSINST(ARSCODFX) - Stock IBM SARSINST(ARSODFXM)


Hopefully, this will save someone a few headaches   ::)
J.

#zOS #AIX #Windows #Multiplatforms
#DB2 #TSM #ODF #zODF #ODWEK
#CapacityPlanning #AFP #ReportDistribution
#Finance

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 607
    • View Profile
Re: Cobol ARSUUPDZ and ODSXUPDZ dynamic exit - V9.5
« Reply #2 on: August 04, 2017, 08:00:39 AM »
Thanks, guy, for posting the resolution.

Ed