Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Create multiple tables without closing the dataset

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF
View previous topic :: :: View next topic  
Author Message
David Robinson

Active User


Joined: 21 Dec 2011
Posts: 182
Location: UK

PostPosted: Tue Nov 19, 2013 5:22 pm    Post subject: Create multiple tables without closing the dataset
Reply with quote

I am running ISPF in batch to create multipe tables in a PDS. It works fine, but I notice that it closes the dataset after each TBCLOSE statement and then has to re-open it for the next one. When this is running in production it will be creating around 20,000 tables so I want the dataset to be opened once at the start and then closed at the end.

TBCLOSE documentation specifically states that "Issuing a TBCLOSE with the LIBRARY parameter for a table is not related to closing the data set allocated to that ddname". But that doesn't seem to be the case.

Any ideas?
Back to top
View user's profile Send private message

enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10327
Location: italy

PostPosted: Tue Nov 19, 2013 5:37 pm    Post subject: Reply to: Create multiple tables without closing the dataset
Reply with quote

You will have to live with that icon_cool.gif
that' s the way ispf table processing works.
Back to top
View user's profile Send private message
prino

Senior Member


Joined: 07 Feb 2009
Posts: 1060
Location: Oostende, Belgium

PostPosted: Tue Nov 19, 2013 5:43 pm    Post subject: Re: Create multiple tables without closing the dataset
Reply with quote

David Robinson wrote:
I am running ISPF in batch to create multipe tables in a PDS. It works fine, but I notice that it closes the dataset after each TBCLOSE statement and then has to re-open it for the next one. When this is running in production it will be creating around 20,000 tables so I want the dataset to be opened once at the start and then closed at the end.

Did anyone actually had some thoughts about an application that uses 20,000 tables...
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Nov 19, 2013 7:34 pm    Post subject:
Reply with quote

Hello,

Sounds like someone had a "solution" and looked about for somewhere to apply the "solution".

How did a 20,000 table alternative even get considered?

If we knew what was being done, we might have alternatives to offer.
Back to top
View user's profile Send private message
don.leahy

Active Member


Joined: 06 Jul 2010
Posts: 658
Location: Whitby, ON, Canada

PostPosted: Tue Nov 19, 2013 8:14 pm    Post subject:
Reply with quote

Have you considered using TBSAVE rather than TBCLOSE? I have not tried it myself, but I suspect that TBSAVE will not close the data set. However, TBSAVE will not close the table, so you might end up with 20,000 open tables at the end of the job. You could try issuing TBEND after TBSAVE, but that may close the data set too.
Back to top
View user's profile Send private message
David Robinson

Active User


Joined: 21 Dec 2011
Posts: 182
Location: UK

PostPosted: Wed Nov 20, 2013 12:58 pm    Post subject:
Reply with quote

Thanks Enrico, at least I wont waste any more time trying to stop it doing what it is supposed to do! I guess the reference in the manual about not closing the dataset must refer to a different scenario.

And thanks everyone else for your input, I think it is time we thought about a fundamental redesign!
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Wed Nov 20, 2013 7:37 pm    Post subject:
Reply with quote

Hello,

Are these tables to be rebuilt for each execution? Will they always be the same?

If the answer to both is yes, you might consider running the table-build process one time and create a new library. Then copy all of these members to the actual tables in the normal run via utility before the actual process begins.

This may help while a redesign is researched.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Copy 4 byte of data from the last rec... arunsoods DFSORT/ICETOOL 9 Fri Oct 06, 2017 12:15 pm
No new posts opening a dataset after reading it fr... arunsoods DFSORT/ICETOOL 5 Wed Oct 04, 2017 3:54 pm
No new posts ejck thru rexx to multiple jobs insid... Susanta All Other Mainframe Topics 5 Tue Sep 19, 2017 1:39 pm
No new posts Create procedure issues -628 when add... chandraBE DB2 1 Mon Sep 18, 2017 12:16 pm
No new posts PLI - printing from multiple programs Pedro PL/I & Assembler 8 Fri Sep 08, 2017 6:36 am

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us