dfhe5_xpi_intro.html |
Last updated: Saturday, 15 June 2019Changes to the exit programming interface (XPI) mean that you might need to change global user exit programs that contain XPI calls. Check whether your global user exit programs are affected by these changes to the XPI, and modify your programs accordingly.
In the loader functions of the XPI, the size of the tokens that are used for the PROGRAM_TOKEN and NEW_PROGRAM_TOKEN options has increased from 4 bytes to 8 bytes. The DFHLDLDX calls affected by this change are ACQUIRE_PROGRAM, DEFINE_PROGRAM, and RELEASE_PROGRAM. If you have used the PROGRAM_TOKEN or NEW_PROGRAM_TOKEN options on these calls in an existing exit program, you must change your exit program to specify suitable locations to contain the larger tokens, and recompile the exit program. Exit programs that do not use the PROGRAM_TOKEN option or NEW_PROGRAM_TOKEN option are not affected.
The size of the token that you specify on the PROGRAM_TOKEN option of the ACQUIRE_PROGRAM call has increased from 4 bytes to 8 bytes. The size of the token returned by the NEW_PROGRAM_TOKEN option has also increased from 4 bytes to 8 bytes. If you have used either of these options in an existing exit program, you must change your exit program to specify suitable locations to contain the larger tokens, and recompile the exit program.
For details, see The ACQUIRE_PROGRAM call.
You can use the REQUIRED_AMODE option of the DEFINE_PROGRAM call to specify the addressing mode of non-Language Environment (LE) AMODE(64) assembler programs.
Also, the size of the token returned by the NEW_PROGRAM_TOKEN option of the DEFINE_PROGRAM call has increased from 4 bytes to 8 bytes. If you have used this option in an existing exit program, you must change your exit program to specify a suitable location to contain the larger token, and recompile the exit program.
For details, see The DEFINE_PROGRAM call.
The SPECIFIED_AMODE option of the GET_NEXT_PROGRAM call now returns the addressing mode of non-Language Environment (LE) AMODE(64) assembler programs.
For details, see The GET_NEXT_PROGRAM call.
The INQ_APP_CONTEXT call now returns the current application context for the most recent application that has been set onto the task.
For details, see The INQUIRE_APP_CONTEXT call and Application context.
The DSA option of the INQ_APPLICATION_DATA call now returns the address of the head of the dynamic storage chain as a 64-bit address.
For details, see The INQ_APPLICATION_DATA call.
The CURRENT_AMODE option of the INQUIRE_CURRENT_PROGRAM call now returns the addressing mode of non-Language Environment (LE) AMODE(64) assembler programs.
For details, see The INQUIRE_CURRENT_PROGRAM call.
The SPECIFIED_AMODE option of the INQUIRE_PROGRAM call now returns the addressing mode of non-Language Environment (LE) AMODE(64) assembler programs.
For details, see The INQUIRE_PROGRAM call.
You can use new options on the INQUIRE_PROGRAM and START_BROWSE_PROGRAM calls to inquire on private programs for applications deployed on platforms. To inquire on private programs for applications deployed on platforms, you must specify the AC_APPLICATION_NAME, AC_MAJOR_VERSION, AC_MINOR_VERSION, AC_MICRO_VERSION, and AC_PLATFORM_NAME fields to provide a complete application context. The SHOW_PROGRAMS option specifies whether to search for private programs only, or both private and public programs.
For details, see The INQUIRE_PROGRAM call.
The size of the token that you specify on the PROGRAM_TOKEN option of the RELEASE_PROGRAM call has increased from 4 bytes to 8 bytes. If you have used this option in an existing exit program, you must change your exit program to specify a suitable location to contain the larger token, and recompile the exit program.
For details, see The RELEASE_PROGRAM call.
You can use the REQUIRED_AMODE option of the INQUIRE_PROGRAM call to specify the addressing mode of non-Language Environment (LE) AMODE(64) assembler programs.
For details, see The SET_PROGRAM call.
Last updated: Saturday, 15 June 2019