H-Series Application Migration Guide (H06.03+)

General Programming Issues
H-Series Application Migration Guide—429855-006
4-4
Adjusting For Increased DCT Limits
number can have up to 16 bits). This change might affect programs that you are
migrating to an H-series system and that call any of the following C-series procedures:
In the G06.23 and later G-series RVUs, the default setting for extended DCT limits is
OFF; that is, the extended limits are not in effect. In the H-series RVUs, the default
setting for extended DCT limits is ON; that is, the extended limits are in effect. This
means that if you have not yet changed any affected applications to allow for the
increased limits, you must do one of the following:
•
Ensure that the system default for the DCT limits extension is reset to OFF (this is
done through an SCF command).
•
Change your program to allow for the increased DCT limits.
The recommended solution is to replace the affected procedures with updated
procedures that can handle the increased DCT limits. The recommended replacement
procedures are as follows:
For more details on the use of the replacement procedures, see the Guardian
Procedure Calls Reference Manual.
C-Series Procedure Extended DCT limits affects calls that:
FILEINFO Use the optional ldevnum parameter
GETDEVNAME (Affects all calls)
GETPPDENTRY (Affects all calls)
GETSYSTEMNAME Use the return value as an ldev or check for specific error
codes
LOCATESYSTEM Use the return value as an ldev or check for specific error
codes
LOOKUPPROCESSNAME Pass a DCT index in the ppd parameter
C-Series Procedure Replacement Procedure
FILEINFO FILE_GETINFOLIST_
GETDEVNAME DEVICE_GETINFOBYLDEV_
CONFIG_GETINFOBYLDEV_
CONFIG_GETINFOBYLDEV2_
FILENAME_FINDSTART_
FILENAME_FINDNEXT_
GETPPDENTRY PROCESS_GETPAIRINFO_
GETSYSTEMNAME NODENUMBER_TO_NODENAME_
LOCATESYSTEM NODENAME_TO_NODENUMBER_
LOOKUPPROCESSNAME PROCESS_GETPAIRINFO_