IBM Support

Further guidance for Content Manager OnDemand exits beyond what's in the V10 readmes

Question & Answer


Question

Is there further guidance for Content Manager OnDemand exits for V10.x?

Answer

The following exits will be invoked AMODE 31 if the module is marked AMODE 31:

SARSINST member

1.arsuupdt DLL

ARSUUPDT (C)

2.arsusec DLL

ARSUSEC (C)

3.arsuperm DLL

ARSUPERM (C)

4.390 indexer INPUT exit

ARSECINP (C)

ARSEXINP (COBOL)

5.390 indexer INDX exit

ARSECNDX(C)

ARSEXNDX(COBOL)

6.390 indexer ANY exit

ARSECANY (C)

ARSEXANY (COBOL)

7.arsodfxa DLL

ARSODFXA(COBOL)

8.arsodfxb DLL

ARSODFXB(COBOL)

9.arsodfxm DLL

ARSODFXB(COBOL)

10.preview exit

ARSUPREC(COBOL)

Needs 10.1.0.3 and PH34486

11.any exit

ARSEXANY(COBOL)

Needs PH18294

     

    

The exits associated with the ARS.PTGN dynamic exit for passtickets and ARSLOG dynamic exit continue to be invoked AMODE 31.

ARS.PTGN

ARSPTGN(HLASM)

ARSLOG

No sample

     

     

Exits associated with ARSYSPIN are still invoked AMODE 31.

Sample ARSYSPIN exits are not available, consult the documentation for directions.

https://www.ibm.com/support/knowledgecenter/en/SSQHWE_10.5.0/com.ibm.ondemand.administeringzos.doc/doday003.htm

    

Any other exits will fail to be invoked if not recompiled to be AMODE 64. For example: the ARSUTBL exit. 

Note that some of the function in the ARSUTBL exit may no longer be necessary because of new function APAR PH12893.

The supplied sample arsuupdt, arsusec, and arsuperm are currently still AMODE 31. If they are already at the V10.1 level, they should work without recompiling/relinking at V10.5.

In addition, a new sample arsusec is now available in 64-bit mode which should provide better efficiency.  This was delivered in APAR PI98845 in SARSINST(ARSUSEC4).

The reason for the better efficiency is that the flow was previously:

Content Manager OnDemand -> ARSUSEC -> ARSUSECX -> dynamic exit facility -> ARSUSECZ

With the new 64-bit exit, extra code is no longer needed to translate 64 -> 31-bit instructions.  The path now is simply:

Content Manager OnDemand -> ARSUSEC4

For 31-bit ARSUSEC and 31-bit ARSUPERM, in V9.5 and below the exits were called with an ODBC connection already established.  APAR PH07363 adds restores this support for V10.1 and above.

For details see: 

https://www.ibm.com/support/pages/apar/PH07363

Starting with V10.1, the OS/390 indexer can invoke its exits via the same DLL mechanism as the other Content Manager OnDemand exits.

In other words, the exits can be compiled as DLLs, and if so the DLLs must reside in the Unix System Services file system.

The DLL versions of the OS/390 indexer exits also have a different set of parameters which are specified in SARSINST(ARSL390X).

The DLL versions of the OS/390 indexer exits can only be invoked AMODE 64.

For compatibility with prior releases, the exits can still reside in a load library. If they reside in a load library, they are not DLLs, they are only invoked AMODE 31, and they will only be passed the old style parameters.

The old style parameters are specified in the SARSINST ARSANYBK, ARSINDBK, ARSINPBK, and ARSIN2BK members

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSQHWE","label":"Content Manager OnDemand for z\/OS"},"ARM Category":[{"code":"a8m0z0000001gP1AAI","label":"technote"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions"}]

Document Information

Modified date:
05 December 2022

UID

ibm11165276

Page Feedback