z/OS Communications Server: IP Network Print Facility
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Starting the NPF VTAM capture point

z/OS Communications Server: IP Network Print Facility
SC27-3658-00

The following shows a sample procedure to start an NPF VTAM® capture point application. You can copy this sample from hlq.SEZAINST(EZAPPAAA) and modify it to suit your environment.
Note: The log file cannot be shared. If you want to run more than one instance of the VTAM capture point application, you will need separate startup procedures with a unique name for each data set in each procedure.
//EZAPPAAA JOB
//*-------------------------------------------------------------------*
//*
//* COPYRIGHT = NONE
//*
//* SMP/E Distribution Name: EZAEC0YS
//*
//* This JCL starts the Network Print Facility's VTAM Capture Point
//* application.
//*
//*   The executable code is assumed to be in a link library which is
//*   in the system link list.  (The default is TCPIP.SEZALINK).
//*
//*   In this sample, below-the-line storage usage is assumed to have
//*   been estimated as follows:
//*      0.5M  - for a minimum-sized application
//*      3.5M  - for storage to handle in-process print files.
//*
//*   The following values in the JCL reflect these assumptions:
//*
//*      The REGION parameter specifies the maximum amount of
//*      below-the-line storage which MVS will allow for this
//*      application.  The 4M value in this sample is the sum of the
//*      two assumed values described above.
//*
//*      The MAXFLSTG subparameter limits the amount of below-the-line
//*      storage which the Network Print Facility will request for
//*      print files which are still in process of being received.
//*      Each open print file uses up 16K of this limit.  The 3584K
//*      value (3.5M) specified in this sample will allow a maximum
//*      of 224 print files to be open at the same time.
//*
//*   TIME is coded with 1440 so we don't time out.
//*
//*   The subparameter LUCLASS is coded (1,2) to pick up any printers
//*   in our LU classes 1 and/or 2.
//*
//*   In this sample, the names of the routing, options and queue
//*   files are:
//*
//*       TCPIP.ROUTING
//*       TCPIP.OPTIONS
//*       TCPIP.QUEUE
//*
//*   All three are assumed to have been created and initialized
//*   prior to the use of this JCL.
//*
//*   The log data set for this sample is TCPIP.VTAM1.LOG.
//*
//*   NOTE: All temporary data sets created by Network Print Facility
//*         will have the high-level qualifier specified via the
//*         defined search sequence.  (See "Configuring NPF Using
//*         TCPIP.DATA and NPF.DATA Statements" in IBM TCPIP for MVS:
//*         Network Print Facility).
//*
//*         In this sample, user specified defaults will be found
//*         in the TCPIP.DATA data set defined by the SYSTCPD DD
//*         statement and in the NPF.DATA data set defined by the
//*         SYSNPFD DD statement.
//*
//*-------------------------------------------------------------------*
//EZAPPAAA EXEC PGM=EZAPPAAA,REGION=4M,TIME=1440,
//         PARM='LUCLASS=(1,2),MAXFLSTG=3584K'
//EZAPPRF  DD DSN=TCPIP.ROUTING,DISP=SHR
//EZAPPOF  DD DSN=TCPIP.OPTIONS,DISP=SHR
//EZAPPQF  DD DSN=TCPIP.QUEUE,DISP=SHR
//EZAPPLOG DD DSN=TCPIP.VTAM1.LOG,DISP=OLD
//SYSTCPD  DD DSN=TCPIP.TCPIP.DATA,DISP=SHR
//SYSNPFD  DD DSN=TCPIP.NPF.DATA,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//SYSMDUMP DD SYSOUT=*

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014