{
{      The purpose of this request is to notify the local access method
{ that the requesting job is performing the network services of
{ APPLICATION_NAME.  The caller, under whose domain the job is running,
{ must be validated to utilize the capability provided by the specified
{ application (see ADMINISTER_VALIDATIONS utility). A server or client of
{ APPLICATION_NAME must have been defined under the MANAGE_RHFAM_NETWORK
{ Utility by a DEFINE_RHFAM_SERVER or DEFINE_RHFAM_CLIENT command and
{ activated by an ACTIVATE_RHFAM_CLIENT or ACTIVATE_RHFAM_SERVER command
{ before sign on is valid.
{
{      A job must sign on for each network service that is provided, with
{ the requirement that each sign on specifies a unique APPLICATION_NAME.
{
{      The scope of a signed on application is job (i.e. all tasks within
{ the job may establish (or acquire) connections on behalf of the signed
{ on application).
{
{      The sign on remains in affect until the job explicitly signs off
{ (via RFP$APPLICATION_SIGN_OFF) or the job is terminated.
{
{
{ RFP$APPLICATION_SIGN_ON(APPLICATION_NAME, APPLICATION_KIND,
{   MAXIMUM_CONNECTIONS, STATUS)
{
{ APPLICATION_NAME: (input) The purpose of this parameter is to identify
{   the application being signed on.  This value must be used by the
{   RFP$REQUEST_CONNECTION, RFP$ACQUIRE_CONNECT_REQUEST, and
{   RFP$ACCEPT_SWITCH_OFFER requests to identify the application service
{   associated with the connection.
{
{ APPLICATION_KIND: (input) The purpose of this parameter is to identify
{   the kind of application being signed on.  The following kinds are
{   allowed:
{
{   rfc$client:  The client application is allowed to establish connections
{     between itself and server applications.  The client can also
{     accept connections that are switched to this application from
{     partner applications.
{
{   rfc$server:  The server application is allowed to acquire incoming
{     connect requests from client applications.  The server can also
{     accept connections that are switched to this application from partner
{     applications.
{
{   rfc$partner:  The partner application kind is only capable of
{     accepting established connections which are switched to this
{     application from cooperating jobs.
{
{     note - the partner application must sign on with the same
{            APPLICATION_NAME as the client or server application that
{            is passing the established connection.
{
{ MAXIMUM_CONNECTIONS:  (input,output) This parameter specifies the
{   maximum number of connections that the specified job can have
{   established, for the specified APPLICATION_NAME, at any instant.
{   Determination of the connection limit is based on application kind:
{
{   rfc$client:  If zero is specified, the number of maximum connections
{     for all instances of the client application specified in the
{     DEFINE_RHFAM_CLIENT command (minus the number of connections currently
{     in use for this client definition) is returned in this parameter. If
{     the value specified exceeds the number of available connections, a
{     status of 'rfe$defined_connects_exceeded' and the actual number of
{     available connections is returned.
{
{   rfc$server:  The connection limit is based on the type of server
{     signing on:
{
{     RHFAM-initiated: The caller must specify the exact number of
{       connections defined per server job in the DEFINE_RHFAM_SERVER
{       command, or a status of 'rfe$max_connection_mismatch' and the actual
{       number of connections per job is returned.
{
{     Non-RHFAM-initiated: If zero is specified, the number of maximum
{       connections for all instances of the server application specified
{       in the DEFINE_RHFAM_SERVER command (minus the number of connections
{       currently in use for this server definition) is returned in this
{       parameter. If the value specified exceeds the number of available
{       connections, a status of 'rfe$defined_connects_exceeded' and the
{       actual number of available connections is returned.
{
{   rfc$partner:  The partner application is subject to the connection
{     limit established when its partner server or client signed on.
{     The MAXIMUM_CONNECTIONS parameter is ignored.
{
{ STATUS:  This parameter returns the results of the request.  If normal,
{   the application has successfully signed on.
{
{      CONDITIONS:  rfe$already_signed_on
{                   rfe$appl_not_active
{                   rfe$appl_not_defined
{                   rfe$defined_connects_exceeded
{                   rfe$invalid_application_kind
{                   rfe$max_connection_mismatch
{                   rfe$system_task_not_active
{      IDENTIFIER:  'RF'
{

