MVSFORUMS.com Forum Index MVSFORUMS.com
A Community of and for MVS Professionals
 
 FAQFAQ   SearchSearch   Quick Manuals   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

File manager, batch and SYSPRINT

 
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> IMS
View previous topic :: View next topic  
Author Message
misi01
Intermediate


Joined: 02 Dec 2002
Posts: 323
Topics: 77
Location: Stockholm, Sweden

PostPosted: Wed Jun 14, 2017 10:23 am    Post subject: File manager, batch and SYSPRINT Reply with quote

I know this sounds pretty crazy, but I'm wondering if anyone can clutch at straws and suggest possible source of this behaviour.

I have my FM job that I run in batch (this is for IMS, but I wouldn't think that that was relevant). Here is the relevant JCL
Code:

//SYSPRINU DD SYSOUT=*,RECFM=FBA,LRECL=133     
//*                                           
//SYSPRINT DD DSN=S1491B.VNOPI00.PRINT,       
//         DISP=(,CATLG,DELETE),               
//         SPACE=(CYL,(5,1),RLSE),             
//         DCB=(RECFM=FBA,LRECL=133)           

The rest of the JCL is identical. I'm flip-flopping the SYSPRINT definitions. If I use the first one, I see the following in SYSPRINT in SDSF
Code:

IBM File Manager for z/OS IMS Component   
ÅÅFILEM SET HEADERPG=NO,PAGESIZE=60       
ÅÅFILEM IBB REGNTYPE=BMP,                 
ÅÅFILEM     PSBTYPE=DYNAMIC,               
ÅÅFILEM     DBDDSN=xxxx.IMS.DBDLIB,       
ÅÅFILEM     DBDMEM=VNOPI00,               
ÅÅFILEM     CRITERIA=Y,                   
ÅÅFILEM     IMSID=IM1B,                   
ÅÅFILEM     IMSOBA=80,                     
ÅÅFILEM     IMSNBA=50,                     
ÅÅFILEM     KEYEXT=N,                     
ÅÅFILEM     PROC=*                         
etc etc etc
                                      DFSUACB0 MESSAGES AND CONTROL STA
         DELETE PSB=FMN0030                                           
DFS0938I DELETE PROCESSING COMPLETE FOR PSB FMN0030                   
                                                                       
DFS0590I END OF ACBLIB MAINTENANCE. HIGHEST CONDITION CODE WAS 00000000

If I use the file as output, all I see is the following
Code:

                                      DFSUACB0 MESSAGES AND CONTROL STA
         DELETE PSB=FMN0033                                           
DFS0938I DELETE PROCESSING COMPLETE FOR PSB FMN0033                   
                                                                       
DFS0590I END OF ACBLIB MAINTENANCE. HIGHEST CONDITION CODE WAS 00000000


The file SYSPRINT has NO error codes such as B37's or similar. I tried running the JCL with smaller amounts of output and saw that file output worked okay when SYSPRINT had 850 rows, but produced nothing when SYSPRINT had 1560 rows.

Is there a magic number somewhere in FM that limits output to, say, 1000 rows ?
_________________
Michael
Back to top
View user's profile Send private message Send e-mail
kolusu
Site Admin
Site Admin


Joined: 26 Nov 2002
Posts: 11797
Topics: 74
Location: San Jose

PostPosted: Wed Jun 14, 2017 11:57 am    Post subject: Reply with quote

misi01,

I am guessing that SYSPRINU is a typo in your JCL. Assuming that it is indeed correct I thing PRTDISP is the culprit here.

Check and add the parm PRTDISP to ensure that all the messages are appended rather than being cleared. If you have PRTDISP=OLD, then the print data set is cleared before each print operation, and print output is written from the beginning of the data set. The default for SYSPRINT DD SYSOUT=* is MOD which is appending the messages.

Code:

$$FILEM SET HEADERPG=NO,PAGESIZE=60,PRTDISP=MOD

_________________
Kolusu - DFSORT Development Team (IBM)
DFSORT is on the Web at:
www.ibm.com/storage/dfsort
Back to top
View user's profile Send private message Send e-mail Visit poster's website
misi01
Intermediate


Joined: 02 Dec 2002
Posts: 323
Topics: 77
Location: Stockholm, Sweden

PostPosted: Thu Jun 15, 2017 1:54 am    Post subject: Reply with quote

The SYSPRINT/SYSPRINU wasn't a typo - it's simply so I can flip-flop between the SYSOUT=* option and the S1491B file.

Unfortunately, your PRTDISP=MOD made no difference (what was interesting to me was that I couldn't find it in the User Guide at all).

In addition, I think this option is only (?) relevant when printing via FMI.
_________________
Michael
Back to top
View user's profile Send private message Send e-mail
Nic Clouston
Advanced


Joined: 01 Feb 2007
Posts: 995
Topics: 6
Location: At Home

PostPosted: Thu Jun 15, 2017 3:59 am    Post subject: Reply with quote

What happens when you pre-allocate your SYSPRINT data set and refer to it with DISP=MOD in your execution?
_________________
Utility and Program control cards are NOt, repeat NOT, JCL.
Back to top
View user's profile Send private message
misi01
Intermediate


Joined: 02 Dec 2002
Posts: 323
Topics: 77
Location: Stockholm, Sweden

PostPosted: Thu Jun 15, 2017 4:18 am    Post subject: Reply with quote

Thought of that and tried it - no improvement. With the file, approx 216 records, with the SYSOUT option, approx 4350
_________________
Michael
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> IMS All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


MVSFORUMS
Powered by phpBB © 2001, 2005 phpBB Group