Greg, we are executing jobs on the mainframe that send out to CMOD for both ACIF and OS/390 indexed reports. with the ACIF defined reports, they can be seen coming across the "Virtual" Printers on the mainframe. In our case, the mainframe "Printers" are defined as PRT8100-PRT8103. After the mainframe jobs completes, we can see the output going across these printers. What determines what printer the jobs uses is defined in the mainframe JCL by specifying DEST=CMOD1 (for PRT8101), CMODBNYM2 (PRT8102) and CMOD3 (PRT8103). We can also log into the production server (Via WINSCP) and look in the ARSLOAD1, ARSLOAD2 and ARSLOAD3 directories to monitor the ACIF collections. We can also track ACIF loads from the SYSTEM LOAD directory on the desktop viewer software we have installed on our PC's. What we are having problems with is identifying how the OS/390 process is configured on both the mainframe and server sides. It doesn't appear to use anything what ACIF uses. We are trying to determine , 1.) Where in the mainframe job it specifies where to send the output to on the mainframe side and 2.) What on the CMOD side triggers the data from the OS390 output to get pulled in to CMOD. Is it coming in via another port on the server? We found the following on both the mainframe and server. On the server side, its under the /usr/lpp/ars/config...Do OS390 loads also somehow use the ARSLOAD process? What precipitated this is, we are going to be doing an upgrade and need to test all load scenarios in DEV environment and we have never loaded any mainframe jobs to DEV using OS/390. We need to determine what needs to be changed to to allow that to happen
.
[@SRV@_DPYCSERR]
HOST=xsa00e70.example.com
PROTOCOL=2
PORT=0
SRVR_INSTANCE=DPYCSERR
SRVR_INSTANCE_OWNER=podep01
SRVR_OD_CFG=/usr/lpp/ars/config/ars.cfg
SRVR_DB_CFG=/usr/lpp/ars/config/ars.dbfs
SRVR_SM_CFG=/usr/lpp/ars/config/ars.cache
[@SRV@_DD]
PROTOCOL=1