Open topic with navigation

TIBCO® Managed File Transfer Platform Server for z/OS 8.1.0

# Defining an APPLID for the Platform Server

You must define an APPLID for use with the Platform Server.

The following is an example of an APPLID definition which can be found in the `APPLMFT` member of the Platform Server `SAMPLIB`.

    **********************************************************************
    *
    *  SAMPLE APPLID FOR SNA COMMUNICATIONS
    *  ==============================
    *
    **********************************************************************
    APPLFUSN VBUILD TYPE=APPL
    FUSNAPPL APPL  AUTH=(NOPO,ACQ,VPACE),                                  -
                   APPC=YES,                                               -
                   ACBNAME=FUSNAPPL,                                       -
                   MODETAB=USERMODE,                                       -
                   SONSCIP=YES,                                            -
                   VPACING=5,                                              -
                   DLOGMOD=#BATCH
    **************************************************************************
    * IF YOU WOULD LIKE TO USE PARALLEL SESSIONS WITH CYBERFUSION YOU SHOULD
    * ADD THE FOLLOWING LINES TO YOUR APPL DEFINITION.  YOU SHOULD
    * UNCOMMENT THE LINES BELOW AND MOVE THEM BEFORE THE DLOGMOD ENTRY
    * IN ORDER TO KEEP THE CONTINUATIONS IN TACT.
    *
    *              PARSESS=YES,     THIS IS NEEDED TO DO PARALLEL SESSIONS -
    *              DSESLIM=10,      PARALLEL SESSION LIMIT                 -
    *              DMINWNR=5,       MINIMUM CONTENTION LOSERS              -
    *              DMINWNL=5,       MINIMUM CONTENTION WINNERS             -
    **************************************************************************

Note: For every major node defined, the VBUILD statement must be placed as the first definition statement.

For more information on defining an APPLID, see the IBM manual: z/OS Communications Server SNA Resource Definition Reference.

Operand | Description
--- | ---
`ACBNAME` | Defines the Access Control Block name. This operand also defines the minor node name for the application. ACB stands for Access Control Block.
`APPC` | Tells VTAM that the application defined here might use the basic functions of LU6.2. This operand is specific to VTAM.
`APPLID` | Defines the name of the application program major node.
`AUTH` | Defines this subsystem to have the ability to acquire an LU (ACQ), and specifies that this subsystem adheres to the methodology of VPACING to LUs (VPACE).
`DLOGMOD` | Defines the name of the default session parameter entry that is used with this application. The session parameters are coded in the `LOGMODE` entry of the `MODETAB` in VTAM. This mode name must also be defined on the remote system.
`FUSNAPPL` | Defines the minor node name to the application. The assigned name must be unique within a network. The default is `FUSNAPPL`, but you can choose the name as you like.
`MODETAB` | Defines the logon mode table to be used to associate each logon mode name with a set of session parameters for the application program if the application program participates as the secondary logic unit (SLU). VTAM searches the logon mode table for the `LOGMODE` that is used by the application when it participates as a SLU. This mode table contains entries that define parameters for SLUs.
`PARSESS` | Specifies that this subsystem can have multiple sessions with other applications on an LU-LU session. If you plan to have multiple simultaneous transfers between two LUs, you have to set this parameter to `YES`.
`SONSCIP` | Tells VTAM that it can terminate sessions with the SLU on behalf of the application.
`TYPE=APPL` | Defines to VTAM that this is an application major node definition. No other optional operands are applicable to define an application major node. `APPL` is also used by default if the `TYPE` operand is not coded. One APPL definition statement is required for each application that is to be identified to VTAM.
`VPACING` | Specifies the maximum number of normal flow requests that another logical unit can send to this session before waiting to receive a pacing response. If this value is too low, it might result in slower transfers.

Copyright © 2003-2021. TIBCO Software Inc. All Rights Reserved.