IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

DSNUTILB - how to stop sysprint?


IBM Mainframe Forums -> DB2
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
lazysurf

New User


Joined: 15 Nov 2005
Posts: 3

PostPosted: Tue Nov 15, 2005 10:29 pm
Reply with quote

Hi,

I'm using the utility DSNUTILB to load data into a DB2 table. Is there a parameter you can use to stop it dumping out loads of messages for each insert I'm doing? Maybe just change the message level to only display proper error messages?

Trouble is that each run I'm doing I'm inserting up to 200,000 rows and it is causing the job output to exceed our maximum limit.

Thanks in advance,

Doug
Back to top
View user's profile Send private message
mdtendulkar

Active User


Joined: 29 Jul 2003
Posts: 237
Location: USA

PostPosted: Wed Nov 16, 2005 6:39 pm
Reply with quote

Doug,

Remove the displays from your program. Use displays only when there is an abnormal condition.

This will solve your problem

Hope this helps

Regards
Mayuresh
Back to top
View user's profile Send private message
lazysurf

New User


Joined: 15 Nov 2005
Posts: 3

PostPosted: Wed Nov 16, 2005 7:25 pm
Reply with quote

Hi Mayuresh,

I'm not sure i understand what you mean by not using Displays. I'm running that IBM utility in a batch job. Its the JCL that calls the utility, not a program.

I'm feeding the utility the following command:

LOAD DATA RESUME YES LOG NO NOCOPYPEND INDDN SYSREC00 INTO TABLE
DB2Z.DB2TABLE

Thanks,
Doug
Back to top
View user's profile Send private message
arunkumar_aruldoss

New User


Joined: 23 Jun 2005
Posts: 1

PostPosted: Wed Nov 16, 2005 11:49 pm
Reply with quote

Hi Doug,

Try using DUMMY keyword for SYSPRINT DD statement.
Back to top
View user's profile Send private message
lazysurf

New User


Joined: 15 Nov 2005
Posts: 3

PostPosted: Thu Nov 17, 2005 4:23 pm
Reply with quote

arunkumar_aruldoss wrote:
Hi Doug,

Try using DUMMY keyword for SYSPRINT DD statement.


Yes, but then I wouldn't get any error messages at all!!! I need any the error messages if it should abend.

I've got round it now by writing the sysprint output to a flat file. Not ideal, but it stops the job exceeding our mainframe job output limits.

Thanks,
Doug
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> DB2

 


Similar Topics
Topic Forum Replies
No new posts Passing SYSPRINT to Invoked Program PL/I & Assembler 9
No new posts Unloading Data from DECIMAL(n,0) Colu... DB2 6
No new posts fetch the record number from FMNMAIN ... CLIST & REXX 10
No new posts How to stop a runaway CICS trans with... CICS 13
No new posts "Standard" SYSIN, SYSPRINT ... PL/I & Assembler 0
Search our Forums:

Back to Top