Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Application file

&pagelevel(3)&pagelevel

The application file supports the mapping between applications and virtual hosts as well as the control of host-aliasing, see section "Operation of virtual hosts".
In addition, the application file can be used to reject and allow connection requests for certain NEA applications. With the command MODIFY-BCAM-OPTIONS you can specify whether the defined rules for connection requests should be applied or not (default: *OFF), see MODIFY-BCAM-OPTIONS / MDBCO: Modify BCAM options (BCAM V25B, #315).

Name and contents of the application file

The name of the application file is set in the DCSTART or DCOPT command with the operand APPLICATION-TABLE (default name $TSOS.SYSDAT.BCAM.APPLICATIONS).

The following syntax rules apply for the file entries used to map applications to virtual hosts:

  • Command lines

    1st character = *:

  • Structure of all the other lines (left to right; no leading blanks permitted)

    • Type of application name:
      Permitted type names: “NEA”, “ISO”, “ISOC”, “SOCKETS” no abbreviations permitted;

    • At least 1 blank

    • alternatively:

      • NEA application name if Type=NEA
        Maximum 8 characters in length. If a shorter name is entered then BCAM inserts it left-aligned and adds x‘40‘ to extend it to 8 characters. The first character must be an uppercase character or ‘$’, ‘#’ or ‘@’; the following characters must be uppercase characters, digits or ‘$’, ‘#’ or ‘@’.
        Alternatively, BS2000 placeholders of up to 32 characters are permitted provided they adhere to the syntax described in the general command description syntax. However, “-s” is not permitted.

        or

      • ISO application name if Type=ISO
        Maximum 5-part name, subdivided by X'00', with a maximum length of 78 bytes.This name is saved as a hexadecimal string. Permitted characters 0-F.

        or

      • ISO application name if Type=ISOC
        Maximum 78-byte name.
        This name is stored as a C string.

        or

      • SOCKETS USER-ID if Type=SOCKETS

        Maximum 8-character user ID. If a shorter name is entered, the remainder is extended to 8 characters using x‘40‘.
        The user ID is only evaluated in the case of applications with STREAMS interface functionality.
    • At least 1 blank

      This means that all socket applications that are started under a corresponding ID are assigned to the same virtual host!

    • Host name
      Maximum 8-character user ID. If a shorter name is entered, the remainder is extended to 8 characters using x‘40‘.
      Host on which the application should be started.
      Entering -NOALIAS prevents host aliasing for the relevant application.


Example



* Example for APPLICATION-TABLE
NEA     TESTAPP              VHOST001
NEA     $FJAM*               -NOALIAS
NEA     $CON<RRR:TTT>E       VHOST8
NEA     <Q:S>EST<30:70>AT    VHOST9
NEA     SAMBA                VHOST001
ISO     5445535400414E57     VHOST002
ISOC    TESTBIRNE            VHOST001
SOCKETS HUHU                 VHOST002


The following syntax rules apply for the file entries for rejecting and allowing connection requests for certain NEA applications:

  • Command lines

    1st character = *:

  • Structure of all the other lines (left to right; no leading blanks permitted)

    • Access rule type
      either blocks a NEA application or defines one or more exceptions to it:
      • Blocking a NEA application:
        • -APP
          causes connection requests for a specific NEA application to be rejected (for example $DIALOG or $FJAM).
          All NEA applications are supported.
          STUNNEL connections are still possible regardless of this configuration.

      • Exception to a blockade:
        • +IP4
          causes connection requests for a NEA application blocked with -APP to be allowed from explicitly specified IPv4 addresses.
        • +IP6
          causes connection requests for a NEA application blocked with -APP to be allowed from explicitly specified IPv6 addresses.
        • +PRO
          causes connection requests for a NEA application blocked with -APP to be allowed from explicitly specified processor names.
    • At least 1 blank

    • NEA application name 
      Maximum 8 characters in length.

    • At least 1 blank

    • Definition of the exception
      for the NEA application (only if access rule is not -APP) for: 

      • IPv4-address if access rule type is +IP4
        possible with and without leading zeros or a mix of both.
        IPv4-address, from which the connection for the NEA application is possible even despite rejection by „-APP“.
      • IPv6-address if access rule type is +IP6
        possible with and without leading zeros or a mix of both.
        IPv6-address, from which the connection for the NEA application is possible even despite rejection by „-APP“.
      • Processor name if access rule type is +PRO
        processor, from which the connection for the NEA application is possible even despite rejection by „-APP“.


Example

* Example of rules for rejecting and allowing connection requests for specific NEA applications
-APP    $FJAM 
+IP4    $FJAM      77.6.100.72 
-APP    $DIALOG 
+IP4    $DIALOG    77.6.100.72 
+IP6    $DIALOG    8701:7ac8:0:9a3:319:8a2e:370:7344
+PRO    $DIALOG    H3PPEXN0