4.2 Determining the i5/OS Object Name of a Process & Function
Process i5/OS Object Names
The OS/400 object name of a process can be determined by displaying the contents of a data area with the same name as the process that is to be directly invoked, in the partition module library.
For example, the process to be invoked is PSLSYS. It resides in partition DEM and the partition module library is DC@DEMOLIB.
DSPDTAARA DC@DEMOLIB/PSLSYS
This will return a screen similar to this:
|
Display Data Area System : SYDASD25 Data area . . . . . . . : PSLSYS Library . . . . . . . : DC@DEMOLIB Type . . . . . . . . . : *CHAR Length . . . . . . . . : 100 Text . . . . . . . . . :
Value Offset *...+....1....+....2....+....3....+....4....+....5 0 'CP@D00001YYNNNNNNN ' 50 ' '
|
The process object name is positioned in bytes 2 thru 9. LANSA allows recursive calling of processes therefore a two digit suffix (01 thru 09) is added to this process name when it is created.
In this case the object name is "P@D00001" and the process's OS/400 object name is:
P@D0000101
If the application demanded that this particular process be called recursively, then subsequent calls would be to programs:
P@D0000102 -> P@D0000109
Note: This name only applies to this process in this partition on this machine. It will vary between CPUs and partitions - such as when it is exported/imported between partitions, LANSA systems, or sites.
Function OS/400 Object Names
The object names of LANSA functions are much easier to determine than process object names.
LANSA functions created with the FUNCTION OPTIONS(*DIRECT) option have the following naming convention:
@FFFFFFF
where:
@ is the prefix FFFFFFF is the function name
That is, the object name is the function name with an "@" symbol as its prefix.
For example, if a function EMPLIST is defined and created with FUNCTION OPTIONS(*DIRECT) specified, its OS/400 object will be @EMPLIST.