RE: Problem with work file

New Message Reply Date view Thread view Subject view Author view Other groups

Subject: RE: Problem with work file
From: Andy Engels (aengels@imrf.org)
Date: Fri Aug 01 2008 - 10:27:14 EDT


It needs to be YES for NATURAL to properly use your disk manager.  They
do all kinds of up-front work looking at your devices.  If it knows the
disk/tape manager is there, it'll work properly........

 --------------------------------------------
Andy Engels
IS Team Leader - Technical Services
Illinois Municipal Retirement Fund
Oak Brook, IL
630-368-5346 


-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of Mike Farmer
Sent: Friday, August 01, 2008 8:33 AM
To: VSE Discussion List
Subject: RE: Problem with work file


Andy,
The FILMNGR=NO
Thanks
MF


 

             "Andy Engels"

             <aengels@imrf.org

             >
To 
             Sent by:                  "VSE Discussion List"

             owner-vse-l@Lehig         <vse-l@Lehigh.EDU>

             h.EDU
cc 
 

 
Subject 
             07/31/2008 04:28          RE: Problem with work file

             PM

 

 

             Please respond to

             vse-l@Lehigh.EDU

 

 





What's  FILMNGR in NTVSE set to?

 --------------------------------------------
Andy Engels
IS Team Leader - Technical Services
Illinois Municipal Retirement Fund
Oak Brook, IL
630-368-5346


-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of Mike Farmer
Sent: Thursday, July 31, 2008 2:15 PM
To: VSE Discussion List
Subject: Problem with work file



When running the following JCL I am getting this Natural error message
from
step 3 when it tries to read in the work file created in step 1
MFSYNCS2 0070 NAT1518 GET or PUT to not openedWORK FILE 1.
If I put a * $$ JOB card between steps 2 and 3 it works but if I try to
run
it as one job it fails with this error.
Is there anything I can do to get it to run as one job or will I have to
make it 2 jobs.  This JCL is just an ad-hoc program I created to
recreate
the error.  In production it is in a large jobstream and this is why I
was
hoping there was a way around splitting it into multiple jobs.
We are on old versions of Natural and VSE, however our syncsort is
current.
Thanks as usual.
MF

* $$ JOB JNM=MFSYNCS,CLASS=J,DISP=D,PRI=3
// JOB MFSYNCS
* ============================================================= *
* STEP 01 MFSYNCX CREATE WORK FILE
* ============================================================= *
// DLBL CMWKF01,'===.WORK.FILE01.050',,SD
// EXEC PROC=NATRUNTE
// EXEC NATBAT,SIZE=NATBAT,PARM='SYSRDR'
BWORKD=(1,1,27,FB)
/*
LOGON LIBA27
MFSYNCS
FIN
/*
* ============================================================= *
* STEP 02 PRINT WORK FILE USING SYNCSORT
* ============================================================= *
// ASSGN SYS001,50F
// DLBL SORTIN1,'===.WORK.FILE01.050',,SD
// EXEC SORT
   OPTION PRINT=CRITICAL,ROUTE=LOG
   RECORD TYPE=F,LENGTH=27
   SORT FIELDS=(8,20,CH,A)
   OUTFIL HEADER2=('EMPLOYEE LIST',3/,
                    1:'NAME',
                   25:'EMPNO',
                   32:'EMPID'/),
          OUTREC=(1:8,20,25:1,1,32:2,6)
/*
* ============================================================= *
* STEP 03 MFSYNC2 READ IN WORK FILE AND PRINT IT WITH NAT PROG
* ============================================================= *
// ASSGN SYS049,50F
// DLBL CMWKF01,'===.WORK.FILE01.050',,SD
// EXEC PROC=NATRUNTE
// EXEC NATBAT,SIZE=NATBAT,PARM='SYSRDR'
PS=60,LS=132
BWORKD=(1,1,27,FB)
BPRINTD=(1,49,133)
/*
LOGON LIBA27
MFSYNCS2
FIN
/*
/&
* $$ EOJ


New Message Reply Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b25 : Thu Aug 07 2008 - 20:50:09 EDT