For reviewing and amending the details stored in these data areas, use the System Settings facility available from the Administration menu and described in Review System Settings.
|
From Byte
|
To Byte
|
Byte Length
|
Type
|
Dec Pos
|
Description
|
|
1
|
10
|
10
|
A
|
|
Name of user defined Program/File error handler.
When a program/file error has been detected, an attempt will be made to call a user defined program/file error handler program during the LANSA program/file error routine. The user defined program/file error handler will provide a means of updating audit/error logs external to the LANSA system.
|
|
11
|
20
|
10
|
A
|
|
Name of user defined Prompt Key message handler program. If the user defined prompt key message handler has been specified for use in the system definition data area DC@A01(position 498 = "Y"), then an attempt will be made to call a user defined prompt key message handler program when the prompt key function key has been selected.
|
|
21
|
560
|
|
|
|
Used for Developer Services Configuration. Refer to Developer Services for more details.
|
|
601
|
610
|
10
|
A
|
|
Import User Exit program name. During a standard import these bytes are tested. If non-blank they are assumed to identify a user exit program that should be invoked each time that an IBM i level object is created or changed during the import. Such a program must receive 3 x Char(10) parameters identifying: (1) the object name, (2) the library, and, (3) the object type (in IBM i "*" style object type notation). This facility is provided only for IBM i.
|
|
611
|
620
|
10
|
A
|
|
Set Environment User Exit program name. After LANSA has set up its environment for the partition these bytes are tested. If non-blank they are assumed to identify a user exit program that should be invoked each time that a LANSA partition is entered. Such a program must receive 3 parameters identifying: (1) the LANSA program library Char(10), (2) the partition id Char(3), and (3) the language code Char(4).
|
|
621
|
630
|
10
|
A
|
|
User Exit program name for SUBMIT command. The first time a LANSA function is submitted these bytes are tested. If non-blank they are assumed to identify a user exit program that should be invoked each time a function is submitted. Such a program must receive one parameter Char(2000) containing the SBMJOB command about to be used. The user exit program can modify the SBMJOB command before exiting and passing back the parameter.(e.g. Add MSGQ() parameter to SBMJOB).
|
|
631
|
638
|
8
|
A
|
|
Target OS Release.
Specifies the TGTRLS value that IBM i compiles are to use. The TGTRLS parameter is appended to LANSA compile and export requests.
Valid values include:
"*CURRENT"
"*PRV"
"VxRyMz" where "VxRyMz" is a valid IBM i version.
"*N" which means that the default for the command is used. New LANSA systems are shipped with this value.
If left blank, the target release used is *CURRENT, not the default for the command.
|
|
639
|
639
|
1
|
A
|
|
Retain task history flag. This can take the values "Y" or "N".
"Y" means that task history is to be retained.
"N" means that the next Request Submit LANSA Re-org job will have Purge Task History starting from date pre-filled with today's date.
|
|
640
|
645
|
6
|
A
|
|
Task tracking category 2 character prefix. The 1st is for task for the system, 2nd is for a task for each user and the 3rd is for task for each "task". Each is optional.
|
|
646
|
648
|
3
|
A
|
|
Task tracking category unlock object after Check In flags. Each flag is 1 character long and its value can be either a "Y", "N" or " ".
The value of this flag determines whether an object is unlocked from the task of this category when the object is checked in. If this flag is "N" or " ", then the normal task tracking object locking applies. The 1st is for task for the system, 2nd is for a task for each user and the 3rd is for task for each "task"
|
|
649
|
668
|
20
|
A
|
|
User exit for Export/Import message logger
649 to 658 must contain library name. It can be *LIBL.
659 to 668 must contain the program name.
The LANSA Export/Import message logger will pass the following parameters and they are as follows:
DC@IDS type (1024) char Output only
Message type (1) char I/O
Message Id (7) char Output only
Message text (132) char Output only
|
|
669
|
688
|
20
|
A
|
|
User exit for LANSA access check to an object.
669 to 678 must contain library name. It can be *LIBL.
679 to 688 must contain the program name.
The LANSA security check programs will pass the following parameter to the user exit program:
DC@IDS (1024) Output Only
Object Name (10) Output Only
Object extension (10) Output Only
Object Type (2) Output Only
Access (2) Output Only
Return Code (1) Input/Output. Valid values Y and N
User Exit Return Code (1) Input/Output. Valid values C and N.
|
|
689
|
708
|
20
|
A
|
|
User exit for IJDT (DC@P8097)
689 to 698 must contain library name. It can be *LIBL.
699 to 708 must contain the program name
The IJDT programs will pass the following parameters to the user exit program:
DC@IDS (1024)
DC@EDS (2500)
Object Name (10)
Object Extension (10)
Object Type (2)
Event code (3)
Message Id (7)
Message file name (10)
Message data (132)
Return Code (1)
User Exit Return Code (1)
Event Source (10)
Event LockInd (1)
Event SubCode (3)
|
|
709
|
728
|
20
|
A
|
|
User exit for CIDT (DC@P8096)
709 to 718 must contain library name. It can be *LIBL.
719 to 728 must contain the program name.
The LANSA CIDT programs will pass the following parameter to the user exit program:
DC@IDS (1024)
DC@EDS(2500)
Object Name (10)
Object Extension (10)
Object Type (2)
Return Code (1) Input/Output.Valid values are Y and N.
User Exit Return Code (1) Input/Output. Valid values are C and N.
Type of call (4) 'CIDT' or 'VTSK'.
|
|
729
|
748
|
20
|
A
|
|
Default value for Export $$DTALIB$$ Substitution Variable. This value is used when export lists are created.
|
|
749
|
749
|
1
|
A
|
|
Y or N. Default value for Prompt user when importing on $$DTALIB$$ substitution variable in export list. This value is used when export lists are created.
|
|
750
|
750
|
1
|
A
|
|
Spare.
|