Special issues when SHARUPD=YES

When files are accessed in the mode SHARUPD=YES, it is possible that a file with a file size of less than 32 GB could become >= 32 GB during processing.

There are two different cases here:

• Callers that are prepared for this situation:

  • by specifying LARGE_FILE=*ALLOWED in the FCB macro

  • by specifying EXCEED-32GB=*ALLOWED in the ADD-FILE-LINK command

• Unprepared callers:
  • by specifying LARGE_FILE=*FORBIDDEN in the FCB macro
  • by specifying EXCEED-32GB=*FORBIDDEN in the ADD-FILE-LINK command

UPAM, FASTPAM and DIV access methods

When a file is accessed with the UPAM, FASTPAM and DIV access methods, the size of the file is checked after each allocator call.
If this check reveals a file size >= 32 GB and the LARGE_FILE=*FORBIDDEN attribute or the EXCEED-32GB=*FORBIDDEN attribute is set in the corresponding TFT, processing is aborted.

• UPAM then issues the following return code

  X'000009AD'     FILE SIZE GREATER 32 GIGABYTES IS NOT ALLOWED

  or the corresponding DMS message

  DMS09AD         FILE SIZE GREATER 32 GIGABYTES IS NOT ALLOWED

• In this instance, FASTPAM issues the following return code in its own parameter list FPAMACC(I)

  X'00400145'     LARGE_FILE_NOT_SPECIFIED
  When a file was accessed in the mode SHARUPD=YES, it was determined that the file size exceeded 32 GB; exceeding 32 GB was not permitted for this file in OPEN.

• In this instance, DIV issues the following return code in its own parameter list DIV(I)

  X'00400030'     LARGE_FILE_NOT_SPECIFIED
  When a file was accessed in the mode SHARUPD=YES, it was determined that the file size exceeded 32 GB; exceeding 32 GB was not permitted for this file in OPEN.

NK-ISAM access method

Under the NK-ISAM access method, the size of the NK-ISAM file is checked on the basis of the extent list located in the file table entry at every SVC entry point. If this check reveals a file size >= 32 GB and if the caller set the LARGE_FILE=*FORBIDDEN attribute in the FCB or the EXCEED-32GB=*FORBIDDEN attribute in the TFT, processing is aborted.

NK-ISAM then issues the following return code

X'00000A23'     FILE SIZE GREATER 32 GIGABYTES IS NOT ALLOWED

or the corresponding DMS message

DMS0A23         FILE SIZE GREATER 32 GIGABYTES IS NOT ALLOWED

The K-ISAM access method is not affected by this problem.