Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Side information for the local application

&pagelevel(4)&pagelevel

For each client application several entries can be created in the upicfile. Each entry defines a local application name with which the client program can sign on to UPIC.

A side information entry for the local client application occupies one line and must have the following format:

LN

local application name

blank

application name

blank

keywords

end-of-line character

2 bytes

8 bytes

1 byte

1-32 bytes1

1 byte



--- optional ---

1For Unix, Linux and Windows systems: With local connection via UPIC local, “application name” can only be up to 8 bytes long.

Description of the entry

  • The line begins with the identifier LN. LN indicates that this is a side information entry for the local client application.

  • local application name
    Here you specify the local application name with which a client program signs on to UPIC. There must be no blank between the identifier LN and the local application name, but the local application name and the application name which follows it must be separated by a blank.

  • application name
    The application name can be up to 32 characters long. The client application signs on to the transport system using the application name.

    UPIC local (Unix, Linux and Windows systems only): The application name can be up to 8 characters long.

  • keywords (optional)
    The following keywords allow you to influence the UPIC-specific values for the local application (see also section “CPI-C terms”) in the upicfile. These keywords allow you to enter addressing information.
    Keywords can be entered after either the application name. You must separate the keyword by a space. You can enter as many keywords as you like and in any order. When entering more than one keyword, you must separate them with a space.

    PORT=listener-port

    The port number is only entered for the address format RFC1006. The port number can be a value between 1 and 65535.

    The value of PORT is used as port number instead of 102.

    An entry in the upicfile can be overwritten using the Set_Local_Port() call.

    UPIC-L (Unix, Linux and Windows systems only): The value of PORT is ignored.

    T-SEL=transport-selector

    Is the transport selector (T-SEL) of the transport address. It must be the same as the entry in the remote system. The transport selector is a name which is up to 8 characters long. The use of T-SEL is optional.

    The value of T-SEL is used. The entry in the upicfile can be overwritten using the Set_Local_Tsel call.

    UPIC-L (Unix, Linux and Windows systems only): The value of T-SEL is ignored.

    T-SEL-FORMAT={T | E | A }

    TSEL-FORMAT is the format indicator of the transport selector. The valid formats are:


    Valid formats for TSEL-FORMAT
    T for TRANSDATA
    E for EBCDIC
    A for ASCII


    The use of T-SEL-FORMAT is optional.

    The value of TSEL-FORMAT is used. The entry in the upicfile can be overwritten using the Specify_Local_Tsel_Format call.

    UPIC-L (Unix, Linux and Windows systems only): The value of T-SEL-FORMAT is ignored.

  • End-of-line character
    The end-of-line character depends on the platform:

    • Windows systems:
      Lines are terminated by a carriage return and line feed (Return key). A semicolon can be optionally used before the carriage return character.

    • Unix and Linux systems:

      The lines are terminated with the <newline> character (linefeed). A semicolon can be optionally used before the <newline> character.

    • BS2000 systems:
      The end of line is represented by a semicolon (;). No spaces are permitted after this.

    If there is a semicolon in a line (contents of the side information entry), UPIC treats this as the end of the line and interprets the rest of the line as a new line (until the next end-of-line character).

A local application name must always be specified for the local application in the Enable_UTM_UPIC call. If there is no entry in the upicfile for this local name or if the entry is invalid, the local name specified with Enable_UTM_UPIC is taken as the application name.

Defining a DEFAULT name

In the upicfile you can define a DEFAULT name for your client application (see also section “Default server and DEFAULT name of a client”). The DEFAULT name is used whenever a client program passes an empty local application name at sign-on (Enable_UTM_UPIC). In the side information entry of the DEFAULT name you enter the value .DEFAULT instead of the local application name. The DEFAULT name entry must therefore have the following format:

LN

.DEFAULT

blank

application name

blank

keywords

end-of-line character

2 bytes


1 byte

1-32 bytes1

1 byte



--- optional ---

1For Unix, Linux and Windows systems: With local connection via UPIC local, “application name” can only be up to 8 bytes long.

Whenever a client program passes an empty local application name at sign-on, UPIC uses this entry and signs the CPI-C program on to the transport access system with the application name specified in application name.

It is possible for several CPI-C programs to sign on to UPIC at the same time with the default name. These programs can even communicate with the same UTM application. But this is only possible if an LTERM pool with CONNECT-MODE=MULTI exists in the UTM application for connection of the client application (see also section “Multiple sign-on to the same UTM application with the same name”).