Remote Call Options

Use the Remote Call options to enable executing a COBOL program remotely from within a PeopleSoft application.

Enter 0 to disable redirection and 1 to enable redirection. Redirection causes the server process to retain intermediate work files that are used to pass parameter values between the server process and a Remote Call/COBOL program for debugging purposes, and it also generates Remote Call trace information in the COBOL output files.

If set to 0, the system generates no COBOL output files. If set to 1 (enabled), the system generates the following files, where <pid> is the Process ID:

rmtcall_in.<pid>
rmtcall_out.<pid>
rmtcall_cblmsg.<pid>
Remote Call Tracing entries for COBOL output files.

Note: RCCBL Redirect should be enabled only when debugging because writing Remote Call trace entries to the COBOL output files can add to system overhead and overall performance.

Remote Call Trace Information

The information captured for Remote Call tracing follows this general structure:

Trace Field	Description
Remote Call trace identifier (RCCT)	Remote Call COBOL Trace (RCCT) helps you to identify the Remote Call tracing in the COBOL output files.
Remote Call Component	Enables you to identify the type of Remote Call being traced: PSPCM PTPECOBL PTPNETRT PTPSQLRT Application COBOL
Trace information	The trace record can be different depending on what is being traced: In some cases there are parameter/value pairs written in the record, such as: `RCCT: PSPCM: pSamParms->szDBName QE850GA RCCT: PTPNETRT: DATA-FIELD-REG BEGIN ->a<- END` In other cases there will be trace information that reports the program flow: `RCCT: PTPNETRT: RemoteCall PSCOBNET function CBL_GET_OS_INFO`

Trace Field

Description

Remote Call trace identifier (RCCT)

Remote Call COBOL Trace (RCCT) helps you to identify the Remote Call tracing in the COBOL output files.

Remote Call Component

Enables you to identify the type of Remote Call being traced:

PSPCM
PTPECOBL
PTPNETRT
PTPSQLRT
Application COBOL

Trace information

The trace record can be different depending on what is being traced:

In some cases there are parameter/value pairs written in the record, such as:

RCCT: PSPCM: pSamParms->szDBName QE850GA
RCCT: PTPNETRT: DATA-FIELD-REG   BEGIN ->a<- END

In other cases there will be trace information that reports the program flow:
```
RCCT: PTPNETRT: RemoteCall PSCOBNET function CBL_GET_OS_INFO
```

Remote Call Output Files

The location and naming of the COBOL output files differ depending on whether the Remote Call is invoked on the application server or the Process Scheduler server (by the PSAESRV server process).

Location	Description
Application Server	If the Remote Call is invoked on the application server, the COBOL output file(s) are written to: `PS_CFG_HOME/appserv/<APP_SERVER_DOMAIN>/LOGS` The output file with the Remote Call trace entries follows this naming convention: `<COBOL_PGM>_<OPERID>_<TIMESTAMP>.out`
Process Scheduler Server	If Remote Call is invoked on the Process Scheduler server (PSAESRV), the COBOL output file will be written to: `PS_CFG_HOME/appserv/prcs/<PROCESS_SCHEDULER_DOMAIN>/log_output/CLB _<Program Name>_<Process_Instance>` The output file with the Remote Call trace entries follows this naming convention: `<COBOL_PGM>_<TIMESTAMP>.out` For example, if a program named PTPTSTAE runs it generates the following: `PS_CFG_HOME/appserv/prcs/HCMPRCS/log_output/CBL_PTPTSTAE_94/PTPECOBL_1121155222.out` Note: PTPECOBL is the initial target COBOL program invoked by the Remote Call function because PTPECOBL handles the parameter passing from the PeopleCode program to the target application Remote Call COBOL program.

Location

Description

Application Server

If the Remote Call is invoked on the application server, the COBOL output file(s) are written to:

PS_CFG_HOME/appserv/<APP_SERVER_DOMAIN>/LOGS

The output file with the Remote Call trace entries follows this naming convention:

<COBOL_PGM>_<OPERID>_<TIMESTAMP>.out

Process Scheduler Server

If Remote Call is invoked on the Process Scheduler server (PSAESRV), the COBOL output file will be written to:

PS_CFG_HOME/appserv/prcs/<PROCESS_SCHEDULER_DOMAIN>/log_output/CLB _<Program Name>_<Process_Instance>

The output file with the Remote Call trace entries follows this naming convention:

<COBOL_PGM>_<TIMESTAMP>.out

For example, if a program named PTPTSTAE runs it generates the following:

PS_CFG_HOME/appserv/prcs/HCMPRCS/log_output/CBL_PTPTSTAE_94/PTPECOBL_1121155222.out

Note: PTPECOBL is the initial target COBOL program invoked by the Remote Call function because PTPECOBL handles the parameter passing from the PeopleCode program to the target application Remote Call COBOL program.

Use this parameter to specify where RemoteCall can find the COBOL executables. By default, RemoteCall looks in a predefined location. This might not be the location where you've installed them on your system:

In UNIX, RemoteCall looks in $PS_HOME/cblbin.
In Windows, RemoteCall looks in %PS_HOME%\cblbin%PS_COBOLTYPE%. The %PS_COBOLTYPE% variable contains a single letter that indicates the character encoding for the database platform. It's automatically set to one of the following values when the application server starts:
- U — Unicode.
- A — Non-Unicode.
- E — EBCDIC.

To override this default behavior, set RCCBL PRDBIN to the absolute path of your COBOL executables, for example:

In Windows: RCCBL PRDBIN=c:\pscobol\MYDOMAIN\cblbin
In UNIX: RCCBL PRDBIN=/app/psoft/MYDOMAIN/cblbin

Note: This parameter doesn't appear in the PSADMIN custom configuration interface if it's not already set. You must define it by editing the application server configuration file directly. On the PeopleSoft Domain Administration menu, select Edit configuration/log files menu, then select Edit psappsrv.cfg (current configuration file) to open psappsrv.cfg in a text editor. Define the RCCBL PRDBIN parameter in the RemoteCall section of the file.