RSC/MP Programming Manual

Access Control Server Developing an ACS
6. Test the ACS by starting the RSC/MP test application for the client workstation.
Ensure that the RSC.INI file for this application is configured for ACS (see
Configuring a Workstation for an ACS on page 9-4). If the RSC/MP test application
runs without an error, the ACS is working correctly.
If the ACS is not configured correctly, the NonStop host or the RSC/MP
workstation reports an error. See the Remote Server Call (RSC/MP) Messages
Manual for further information about these returned errors.
Developing an ACS
This subsection provides general ACS development information.
COBOL Programming Considerations
When designing an ACS in COBOL, note that:
ACS processes are opened by the TDP with syncdepth equal to 1 and no waited
I/O depth equal to 15.
User IDs and password strings are NULL-terminated.
ACS Header
The ACS header, RSC_ACS_HEADER, is included in the RSC.H file. You can use this
header in your ACS application code.
/*
* Access Control Server definitions.
*/
The access control server (created and maintained by the user)
should expect a message (from the TDP) as defined below:
typedef struct
{
SHORT
nResult;
USHORT
uVersion;
USHORT
uSessionType;
CHAR
acUserId
[ RSC_USERID_SIZE ];
CHAR
acPassword
[ RSC_PASSWORD_SIZE ];
USHORT
uServerCount;
CHAR
acAcsMessage
[ RSC_ACS_MESSAGE_SIZE ]
} RSC_ACS_HEADER;
where each value is define as:
nResult
The result code that the ACS sets to indicate whether the user ID and password
were authenticated. If this result code is set to nonzero, the TDP returns an API
security error on the RscBeginSession function call.
HP NonStop Remote Server Call (RSC/MP) Programming Manual — 522360-006
9- 8