News Site map Partner login Jobs Web shop
Home Solutions Support Downloads Search Contact About MPI Tech
Page path: Home Solutions Mainframe & AS/400 printing Mainframe software solutions EPM
EPM - Enterprise Print Manager
Overview Data sheet Manuals Support Contact

EPM - Enterprise Print Manager

EPM™ Upload

EPM™ Upload for Windows NT or 2000 installation & operator's guide.

Features:

  • Print Windows/workstation output (client environment) on host OS/390 EPM™ printers
  • Use Windows NT or 2000 and print spooler for host printing
  • Provide notification of print complete
  • Control and monitor printing status of uploaded print
  • Enable drag and drop printing, and native Windows print submission to host EPM™ printers
  • Translate, upload and submit JCL from Windows NT or 2000

Components

The EPM™ Upload for Windows NT or 2000 consists of 4 components:

  • The Upload Port Monitor which is the minimum installation of the EPM™ Upload installation wizard.
    This port monitor provides the ability to print from the workstation platform (client environment) to host printers.
  • The PrintStatus Application, which is included in the typically installation of the EPM™ Upload installation wizard.
    This application makes you able of viewing and changing the status of a print job, after it has been successfully upload to the OS/390 environment.
  • The Upload Application which is included in the typically installation of the EPM™ Upload installation wizard.
    This application enables you to translate and upload textfiles to the OS/390 environment.
  • The Internal Reader Application which is included in the typically installation of the EPM™ Upload installation wizard.
    This application enables you to translate and upload JCL to the OS/390 environment.

EPM™ Upload Port Monitor

Overview

The EPM™ Upload print facility provides the ability to print from the workstation platform (client environment) to host printers. The clients' selects a printer output device that will be used for printing, and subsequently can use this printer of any print output. A workstation software print queue port monitor is used to communicate with EPM™, and transfer the print data to the host spool system (via TCP/IP). EPM™ (or other print systems) can subsequently process the print job as if it had been submitted from the host system.

  • Use EPM™ print facilities (for workstation print)
    EPM™ provides a number of functions that can be useful for workstations generated print.
    • Print distribution (broadcast queues)
    • Default print formatting
    • Print to user's default printer
    • Synchronous printing

Upload and Print Requirements

  • Input data stream support (types)
    • Formatted output (PCL/PostScript) on EPM™ printers.
      Typical workstation print is formatted in PCL or PostScript for a specific printer device type. The upload and print mechanism should therefore support pre-formatted print datastreams that can be treated as "transparent print data"
    • AFP
      with the use of an AFP printer driver (available free from www.printers.ibm.com/r5psc.nsf/web/afpdr), AFP print data can be generated from any workstation based print application. Implementation and use of enterprise wide print resources can be implemented to improve print consistency and portability from workstation environments to other platforms. Use of AFP also increases the range of output formats and options (e.g. view/archive) that are available for printing
  • Print Data stream selection
    • The local Windows NT or 2000 print queue is designed to address an individual host printer, with the exception of "default" print queue selection. during installation of the Windows NT or 2000 port monitor, selection of the host printer device (and there by supported print data stream) is made.
  • Upload to JES spool
    • Print jobs are uploaded to EPM™, which can in turn deposit print output to JES spool.
  • Server platforms
    • Upload and print server.
    • To eliminate any specific requirements to the workstation client environment, a Windows NT or 2000 print queue can be used to service client print requests (using the Windows NT or 2000 printer sharing method).
    • Windows NT or 2000 print queue port monitor
      The Windows NT or 2000 machine which will be used to perform host communication must also be used to direct client print output. Print output and queue management will be performed using the Windows NT or 2000 standard features and functions (e.g. client queue definition, user authorization, driver distribution etc.). No specific client software is therefore required.
    • Host Connectivity (pre-requisite)
      A TCP/IP attachment is required between the server where the upload and print facility is located and the OS/390.
    • Remote Print Server
      The EPMRMAPI program operates on the S/390 host as a started task and receives print requests from the Windows NT or 2000 port monitor via a TCP/IP socket. Print requests are received, and forwarded to EPM™ within the sysplex complex. up to 2000 printers can be supported using this program (multiple versions of this program can be started if needed).
  • Client platforms
    • Windows clients
      the target native environment assumes use of a Windows NT or 2000 print server as a standard component. This environment support client printing requests from both Windows 16 bit (Win 3.11) and 32 bit clients (Win 95/98/NT/2000).
  • Host Printer Selection
    • Selection of target EPM™ host printer can be performed using one of two options. Host printer selection is performed during installation of the Windows NT or 2000 print queue.
    • Local Print Queue (Printer Specific Queue).
      The client is able to select a local print queue. A one to one print queue mapping of local queues to host printers determined will be performed. (i.e. all print directed to a specific local print queue will be directed to a specific host printer).
    • Default Printer (Public Queue).
      The client is able to select a default host printer for upload. The selection of a default printer will be determined based upon the user identification (user name), and the functions provided by EPM™ and user default printer associations.

Typical Installation and Print Scenario

The EPM™ Upload and Print Program is designed to be operated as a started task using an authorized program (installed in an authorized proclib). RACF or other security systems authorization rules are required to be generated for to permit print job submission. This requires that the Windows logon userid is defined to RACF or other security system.

Installation consists of the following steps:

  • Installation of the EPMRMAPI program:
    1. Install program object module (Authorized program)
      The program installation can be used by link editing the program into a target load library. The BLDALL JCL executed during installation performs this operation for the program EPMRMAPI module.
    2. Install the startup proc member
      The following startup EPMRMAPI JCL procedure can be installed into a suitable authorized proclib. The following notes apply to the program parameters:
      • HLQ (High Level Qualifier)
        The data set high level qualifier used to define the EPM™ authorized program link library.
      • LLQ (Low Level Qualifier)
        The data set low level qualifier used to define the EPM™ authorized program link library.
      • SUBSYS
        The SUBSYS value indicates the subsystem name of the enterprise print manager that will be used together with the upload and print program. This value should correspond to the EPM™ subsystem name (i.e. specified in the EPM™ startup procedure SUBSYS JCL keyword). (The Enterprise Print Manager is required to be active within the same system image.
      • SMFTYPE
        This parameter is used to indicate if SMF recording will be performed for the upload and print program. A value of 0 indicates that SMF recording is disabled. Refer to "Enterprise Print Manager Product Installation Guide, VTAM and TCP/IP User Interface Accounting" for additional details.
      • LOGNAME (default EPMRLOG)
        This parameter can be used to change the DDNAME of the program log data set.
      • TCPIP (default TCPIP)
        This parameter can be used to change the name of the TCP/IP program address space.
      • PORT(default 15000)
        This parameter is used to specify the TCP/IP port that will be used to listen for TCP/IP connection requests via the Windows NT or 2000 upload and print port monitor. If multiple instances of the upload and print program will be used, they should be assigned different port numbers.

    The following diagram illustrates the EPMRMAPI Proc JCL.

    //EPMRMAPI PROC HLQ=YYYYY,LLQ=EPM110,SUBSYS=SPS1,
    //SMFTYPE=99,LOGNAME=EPMRLOG,TCPIP=TCPIP,PORT=15000
    //EPMRMAPI EXEC PGM=EPMRMAPI,TIME=1440,REGION=0M,
    //PARM='&SUBSYS,&SMFTYPE,&LOGNAME,&TCPIP,&PORT'
    //STEPLIB DD DISP=SHR,DSN=&HLQ..&LLQ..LINKLIB
    //EPMRLOG DD SYSOUT=*

    The Upload and Print program can be started from the MVS console using the S procname command. An initialization complete message is indicated when the program has been started.

    S EPMRMAPI
    IRR812I PROFILE ** (G) IN THE STARTED CLASS WAS USED 166
    TO START MAPIRMO WITH JOBNAME EPMRMAPI.
    /HASP100 EPMRMAPI ON STCINRDR
    IEF695I START EPMRMAPI WITH JOBNAME MAPIRMO IS ASSIGNED TO USER ...
    , GROUP SYS1
    /HASP373 EPMRMAPI STARTED
    IEF403I EPMRMAPI - STARTED - TIME=11.46.57
    EPI001I EPM UPLOAD READY FOR PRT LOGON

  • Upload and Print Windows NT or 2000 port monitor
    1. Upload and Print Queue installation
      The Windows NT or 2000 print queue and upload and print port monitor is required to be installed on a Windows NT or 2000 server machine. Iconsists of initial installation of software components, and customization. Values that need to be configured are:
      • EPM™ IP address, and IP Port Number.
      • Printer queue name.
    2. Upload and Print Customization.
      Customization consists of the following tasks:
      • Create a local print queue that uses "user name" for print requestor identification.
      • Client Installation.
      • The following installation sequence assumes use of a Windows 95/98 or NT or 2000 client
      • Printer discovery. Using the Windows discovery of the neighborhood network, a print queue is selected (that is resident on the Windows NT or 2000 server where Upload and print server is installed).
      • Driver Installation. A pre-requisite printer driver, and local print queue are defined on the client machine (that match the installed Windows NT or 2000 server print queue).
    3. Print submission to local print queue.
    4. print to host printer.
      Print jobs are submitted using the local printer definition. The print job is deleted in the local print queue once the print job is uploaded.
    5. Upload.
      The Windows NT or 2000 print queue submits a print request to the host EPM™ and transfers the print job for printing. Dependent on the print queue configuration, various print job submission options can be used.
    6. EPM™ printing.

The print job is selected by the target printer device, and printed.

Upload and Print Operation

Printing to the upload and print queue can be performed from the local Windows NT or 2000 machine. In addition, if you use the Windows Printer Sharing function, the print queue can be made available to other users on other Windows platforms (e.g. Windows 95/98 etc). Remember that the Windows userid for these other machines must be defined on the host system in RACF or other security system.

A single print queue with the upload and print port monitor can be used for printing to a wide range of host printers. Use of this function requires that the "DEFAULT" printer is selected as the printer name. In addition, each user must have a default printer defined in a userdef entry (or group entry) in the EPM™ profile.

In the event that an error occurs during print submission, a popup message will be displayed on the Windows NT or 2000 machine.

After a print job has been spool, and successfully transmitted to the EPM™, the print job is deleted from the Windows NT or 2000 print queue.
The print job is no longer visible at the Windows NT or 2000 print queue, but by using the PrintStatus application you are able to see the status of your print job in the host spool system.

PrintStatus Application

Overview

The PrintStatus application provides the ability to view and change the status of succesfully uploaded print job at the OS/390 environment. You can choose among the Windows NT or 2000 print queues that use EPM™ Upload Port Monitor.

  • The PrintStatus application provides a number of functions that can be useful for workstation generated print.
    • View the print job's status.
    • Change the print job's status.
    • Change other print job's status.
    • Start/stop the printer device.

    PrintStatus Application Requirements

    • Server Platforms.
      • Windows NT or 2000 Print Queue Port Monitor.
        You need to install at least one print queue on your Windows NT or 2000 that use the EPM™ Upload Port Monitor, to have any Windows Print Queue's to select.
      • Host Connectivity (pre-requisite).
        A TCP/IP attachment is required between the server where the PrintStatus application is located and the OS/390.
      • Remote Print Server.
        The EPMRMAPI program operates on the S/390 host as a started task and receives print requests from the Windows NT or 2000 Port monitor via a TCP/IP socket. Print requests are received, and forwarded to EPM™ within the sysplex complex. Up to 2000 printers can be supported using this program (multiple versions of this program can be started if needed).
    • Client Platforms.
      • Windows client.
        This application will only run under Windows NT or 2000, where an EPM™ Upload Port Monitor is installed, use as a minimum one Windows NT or 2000 print queue using the EPM™ upload Port Monitor is installed.
    • Printer Selection.
      • From the PrintStatus application you can select any of your EPM™ Upload Print Queues, and view the queued files.

    Typical Installation and PrintStatus Scenario

    The following sequence of activities is required to install the PrintStatus application.

    • EPM™ Upload Port Monitor installation, Typically or custom and choosing installation of the PrintStatus application.

      • Values that need to be configured are:

      • EPM™ IP address, and IP port number.

      Values that can be configured are:

      • The PrintStatus application refresh time.
        This value can be set in a range of 5 - 300 seconds.

    Upload Application

    Overview

    The Upload Application provides the ability to print from the workstation platform (client environment) to host printers. You can from any application call this application to upload your files to the OS/390 environment. You can drag and drop a file on the Upload Applicationīs icon, or you can click-right at a text file, and select the option upload to epm, to start the upload dialog.
    You can select the option "use translate", this will translate your text-files to EBCDIC, before uploading them to the OS/390 environment.

    • The Upload Application provides an opportunity of uploading any file to the host printer devices.
      From any application you can call the Upload Application with a parameters as listed below.

      Or by starting the application, dragging and dropping, a file to the application, or clicking right on a txt-file and selecting the Upload to EPM option menu item, you get a dialog where you can type in the parameters listed below.
      • HostAddress, the IP address of the OS/390, where the remote print server is running.
      • HostPort, the IP port number, the remote print server is listening at.
      • Translate the file before uploading, select this option if you want the applicaiton to translate you txt-file to EBCDIC before uploading it.
      • PrintFile, the name an location, of the file to be uploaded to the OS/390 environment.
      • Translate tabel, you can either use the default translate table, to translate ASCII characters to EBCDIC, or you can add your own.
      • Show success upload dialog, this option will show a dialog telling you that the upload was done succesfully, if so, if this option is not selected you will only get a dialog after uploading in the case that an error occured.
      • Jobname, the name in the OS/390 environment of your print job.
      • Sysplex, the name of the sysplex where the printer device is defined.
      • PrinterName, the name of the printer you want to print you print job.
      • Destination, the destination of your print job.
      • PrMode, the Print mode, you want assigned to the print job.
      • Writer, you can specify the Writer you want assigned to the print job.
      • Class, you can specify the Class you want assigned to the print job.
      • Forms, you can specify the Forms you want assigned to the print job.
      • PageDef, you can specify which PageDef you want the printer to use, when printing the print job.
      • FormDef, you can specify which FormDef you want the printer to use, when printing the print job.

    Upload Application Requirements

    • Server Platforms.
      • Host Connectivity (pre-requisite).
        A TCP/IP attachment is required between the server where the PrintStatus application is located and the OS/390.
      • Remote Print Server.
        The EPMRMAPI program operates on the s/390 host as a started task and receives print requests from the Windows NT or 2000 port monitor via a TCP/IP socket. Print requests are received, and forwarded to EPM™ within the sysplex complex. Up to 2000 printers can be supported using this program (multiple versions of this program can be started if needed).
    • Client Platforms.
      • Windows client.
        This application will only run under Windows NT or 2000.

    Internal Reader Application

    Overview

    The Internal Reader Application provides the ability to upload JCL from the workstation platform (client environment) to JES input queue. you can drag and drop a file on the Internal Reader Applications icon, or you can click-right at a file, with extension JCL, and select the option upload JCL to JES, to start the Internal Reader Dialog.

    • The Internal Reader Application provides an opportunity of uploading any file to the JES.
      Starting the application by dragging and dropping, a file to the application, or clicking right on a JCL - file and selecting the Upload JCL to JES option menu item, you get a dialog where you can type in the parameters listed below:
      • HostAddress, the IP address of the OS/390, where the Remote Print Server is running.
      • HostPort, the IP Port Number, the Remote Print Server is listening at.
      • JCL-file, the name an location, of the file to be uploaded to the JES.
      • Translate Tabel, you can either use the default Translate table, to translate ASCII characters to EBCDIC, or you can add your own.
      • Show success upload dialog, this option will show a dialog telling you that the upload was done succesfully, if so, if this option is not selected you will only get a dialog after uploading in the case that an error occured.
      • Password, if the EPMRMAPI task, has been started, with the option password required, you will be promted for you password be starting the upload.

    Internal Reader Application Requirements

    • Server platforms.
      • Host Connectivity (pre-requisite).
        A TCP/IP attachment is required between the server where the PrintStatus application is located and the OS/390.
      • Remote Print Server.
        The EPMRMAPI program operates on the s/390 host as a started task and receives print requests from the Windows NT or 2000 port monitor via a TCP/IP socket. Print requests are received, and forwarded to EPM™ within the sysplex complex. Up to 2000 printers can be supported using this program (multiple versions of this program can be started if needed).
    • Client Platforms.
      • Windows client.
        This application will only run under Windows NT or 2000.
© 2002-2007 MPI Tech