Installing and Configuring Platform Server XCOM Interface

The platform server XCOM interface is installed when TIBCO MFT Platform Server for z/OS is installed.

You must perform a single step to assemble the XCOMDFLT options table. This is the same XCOMDFLT table that is assembled when XCOM is installed at an installation.

Procedure

  1. Copy the XCOMDFLT member into the platform server SAMPLIB.
    If you want, you can use the platform server default XCOMDFLT table that already exists in the platform server SAMPLIB.
    Note: Because most XCOM parameters are ignored by the platform server, it might be easier to update the supplied XCOMDFLT member.
  2. Make any changes to the XCOMDFLT table to configure it for the platform server.
    Following are the parameters that require changes:
    • JOBACB: points to the name of the VTAM ACBs defined to the platform server.
    • ACBNAME: points to ACBNAME of the platform server started task.

    Add the following new platform server parameters to #DFLTAB:

    FUSION_STCOVER={ YES/NO}
    • If this parameter is specified as YES, then the ACBNAME name overrides the STCAPPL parameter normally defined in the PARM JCL statement. The STCAPPL statement is ignored when FUSION.STCOVER=YES is defined. This is done so that a user can submit the same JCL, except that the STEPLIB will point to the platform server library, and the platform server request is routed to the platform server started task, not to the XCOM started task.
    • If this parameter is specified as NO, the STCAPPL statement on the PARM JCL statement overrides the ACBNAME defined to the XCOMDFLT table.
  3. Assemble the XCOMDFLT table.
    You can use any assembly JCL. The following changes must be made to the JCL to assemble the platform server XCOMDFLT module:
    • Ensure that the SYSIN DD statement points to the XCOMDFLT in the platform server SAMPLIB.
    • Ensure the SYSLIB DD statement of the Assembler step points to the platform server SAMPLIB data set.
    • Ensure that the XCOMDFLT module is linked into the platform server LOADLIB data set with the name XCOMDFLT.

    At this point, the platform server XCOM interface is ready to use. The platform server XCOM interface program is called FUSXJOB. This program has an alias of XCOMJOB.

    To run the platform server XCOM interface, you must change the STEPLIB of the program to use the platform server loadlib. That way, when program XCOMJOB is executed, the platform server program is executed instead of the XCOM program.

    As stated before, the platform server XCOM interface accepts XCOM parameters and creates a platform server transfer request. After the transfer parameters are read, only platform server protocols are used, which means the following things:
    • The remote computer must have a version of platform server installed. The platform server does not communicate with the XCOM started task.
    • The messages displayed are platform server messages, not XCOM messages.

    The PARM fields that are ignored by the platform server XCOM interface are COMPNEG, DISPALG, DUMPCL, EDESC, EROUT, GROUP, IDESC, IROUT, LOG, LOGCLASS, LOGDEST, LOGMODE, and LU.

    The SYSIN01 fields that are ignored by the platform server XCOM interface are DISP, DROPSESS, EPRTY, LPASS, LUSER, REPORT, REPORTHOLD, RESTART, RNOTIFY, RNOTIFYNAME, SPRTY, TRUNCATE, USER, and PACK.

    The SYSIN01 fields that will cause the platform server XCOM interface to terminate with a return code 40 (0x28) are DEN, EXPDT, LABEL, LLABEL, LUNITCT, LVOLCT, LVOLSQ, RETPD, UNITCT, VOLCT, VOLSQ, CHARS, SPOOL, HOLDCOUNT, XTCERRDECR, XTCERRINCR, XTCERRREL, XTCERRPURGE, XTCGOODDECR, XTCGOODINCR, XTCGOODREL, XTCGOODPURGE, XTCJOB, and XTCNET.

    See the following example of the JCL required to run the platform server XCOM interface: 
    //jobname JOB  ,'C-Fusion’,MSGCLASS=X,REGION=5M,CLASS=A   
//S1SCH    EXEC PGM=XCOMJOB,                                            
//  PARM='TYPE=SCHEDULE,ACBNAME=FUSN,GROUP=NYACCT'                      
//STEPLIB  DD  DISP=SHR,DSN=FUSION.LOADLIB                         
//XCOMLOG  DD  SYSOUT=*                                                 
//XCOMINQ  DD  DSN=yourdsn,DISP=SHR                             
//SYSIN01  DD  *                                                        
TYPE=SEND                                                               
CODE=TEXT                                                               
RECSEP=YES                                                              
LFILE=LOCAL.TEST.DATA 
FILE=REMOTE.TEST.DATA
USERID=ABC123
PASSWORD=XYZ
//
    Though you are using the platform server XCOM interface, you can still use some platform server features. For example, instead of the USERID and PASSWORD parameters defined in the previous example, you can use the platform server user profile feature. The USERID and PASSWORD parameters are replaced by the following parameter:

    USERID=*PROFILE

    That way, the clear text password does not have to be displayed in the JCL.

    See the following output that is displayed after executing the previous job: 
    TYPE=SEND                                                                           
CODE=TEXT                                                                           
RECSEP=YES                                                                          
LFILE=LOCAL.TEST.DATA
FILE=REMOTE.TEST.DATA                                                           
USERID=ABC123
PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXX                                                                     
PGTX4512I Activity I414000000 Queued to MFT Platform Server started task                         
PGTX4510I Successful Requests=1  Failed Requests=0  Timeout Requests=0              
PGTX4511I FUSXJOB ending with Return code 0
    If TYPE=EXECUTE is requested instead of TYPE=SCHEDULE, the following messages are displayed in the XCOMLOG data set: 
    TYPE=SEND 
CODE=TEXT                                                                           
RECSEP=YES                                                                          
LFILE=LOCAL.TEST.DATA
FILE=REMOTE.TEST.DATA                                                           
USERID=ABC123
PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXX 
PGTX4512I Activity I414000002 Queued to MFT Platform Server started task 
PGTX4521E Activity=I414000002  Status=ACTIVE    Record Count=0  Byte Count=0 
PGTX4521E Activity=I414000002  Status=COMPLETE  Record Count=3200 Byte Count=259200  
PGTX4510I Successful Requests=1  Failed Requests=0  Timeout Requests=0 
PGTX4511I FUSXJOB ending with Return code 0