Previous Topic: Sample 2Next Topic: Storing Distributed Files in a CA Dispatch Data Repository


Sample 3

In the third example, the RegionalSales.doc file was transferred to the SYSA TCP/IP host for processing. The LPDDEST statement was coded as follows:

LPDDEST QDEST=SALESPR1,FAM=SAR,FFIEXT=&N9,FNAME=SALES,FOPTS=B,FSAR=CAI.VIEW

The following LPR command was entered:

>LPR -Ssysa -Psalespr1 RegionalSales.doc

In the LPDDEST statement, the FNAME parameter is hard-coded with a value of SALES and is not using variable substitution.

VIEW 2.0 ALL ---------------- SYSOUT SELECTION LIST ---------------------------- COMMAND ===>        SCROLL ===> CSR SEL ID            JOBNAME      JOBID    ARCH DATE/TIME LOC    LINES  PAGES XCODE     SALES         ESFSTC                11/20/03 15:31 DISK       5      0

In this example, the report ID is the value specified on the FNAME parameter, which is hard-coded as SALES. This value is used for all reports that are transferred to this destination, regardless of the source file name. (The original source file name (RegionalSales.doc) is still available for informational purposes in the description field.) Also, no J parameter was specified on the LPR command, so JOBNAME defaults to the name of the CA Spool started task (ESFSTC).

These files cannot be opened in 3270 mode through CA View. To view these files, they must be accessed cooperatively through CA OM Web Viewer.

Note: For additional information about the LPDDEST statement and the use of dynamic value parameters, see the chapter "Configuration" in this guide. For more information about LPR commands, see the CA LPR Installation Guide.