To use LAUNCHER Office API programs, the programs parameters must be strictly declared.
AS/400 programs variables statement :
LAUNCHER Office programs require input and output parameters.
|
Name |
Type |
Size |
Description |
|
HANDLE |
CHAR |
50 |
Conversation ID between job and PC. |
|
SOVRAN |
CHAR |
30 |
Target PC Name or IP address. |
|
CCSID |
CHAR |
10 |
AS/400 job CCSID. |
|
CMD |
CHAR |
10 |
Command send to PC Verb. |
|
OPT |
CHAR |
1 |
Command Option. |
|
PARM1 |
CHAR |
512 |
Command Parameters. |
|
PARM2 |
CHAR |
1024 |
Command Parameters (Complements) |
|
RESULT |
CHAR |
512 |
PC returned Result. |
Also see : Command PROPERTY
Statements examples :
CL :
DCL VAR(&HANDLE) TYPE(*CHAR) LEN(50) VALUE(‘*ONLY’)
DCL VAR(&SVRADD) TYPE(*CHAR) LEN(30) VALUE(‘*DEV’)
DCL VAR(&CCSID) TYPE(*CHAR) LEN(10) VALUE(‘*JOB’)
DCL VAR(&CMD) TYPE(*CHAR) LEN(10)
DCL VAR(&OPT) TYPE(*CHAR) LEN(1)
DCL VAR(&PARM1) TYPE(*CHAR) LEN(512)
DCL VAR(&PARM2) TYPE(*CHAR) LEN(1024)
DCL VAR(&RESULT) TYPE(*CHAR) LEN(512)
RPG ILE :
DHANDLE S 50 inz(‘*ONLY’)
DSVRADD S 30 inz(‘*DEV’)
DCCSID S 10 inz(‘*JOB’)
DCMD S 10 inz(‘*DEV’)
DOPT S 1 inz(*blanks)
DPARM1 S 512 inz(*blanks)
DPARM2 S 1024 inz(*blanks)
DRESULT S 512 inz(*blanks)
All commands may return errors messages through the standard AS/400 errors managing process. These messages are identified with a MSGID : LNCnnnn.
Exemple :
The following example opens a single connection (&HANDLE value is *ONLY) on PC housing the calling emulator (using *DEV device) and the current job CCSID.
|
DCL |
VAR(&HANDLE) TYPE(*CHAR) LEN(50) |
|
DCL |
VAR(&SVRADDR) TYPE(*CHAR) LEN(30) |
|
DCL |
VAR(&CCSID) TYPE(*CHAR) LEN(10) |
|
|
|
|
CHGVAR |
VAR(&HANDLE) VALUE('*ONLY') |
|
CHGVAR |
VAR(&SRVADDR) VALUE('*DEV') |
|
CHGVAR |
VAR(&CCSID) VALUE('*JOB') |
|
|
|
|
CALL |
PGM(LNCOPEN) PARM(&HANDLE &SVRADDR &CCSID) |
|
MONMSG |
MSGID(LNC0000) EXEC(GOTO CMDLBL(ERROR)) |