View previous topic :: View next topic |
Author |
Message |
shootingstar Beginner
Joined: 19 Sep 2004 Posts: 14 Topics: 11 Location: Dallas, TX
|
Posted: Sun Sep 19, 2004 9:04 pm Post subject: Need to create a member in a PDS via program logic - not JCL |
|
|
I have a process I am designing for automating maintenance of a huge DB2 database (125 billion rows). I am creating JCL dynamically within one of the programs and I need to write the JCL to a PDS as a new member. Can anyone offer any suggestions as to how to approach this? COBOL or assembler would be fine. REXX is probably not an option.
Any help would be appreciated. |
|
Back to top |
|
 |
semigeezer Supermod
Joined: 03 Jan 2003 Posts: 1014 Topics: 13 Location: Atlantis
|
Posted: Sun Sep 19, 2004 9:55 pm Post subject: |
|
|
using bsam assembler macros... open, put, put,put, ... close, stow. If you need to allocate the data set as well, then use SVC99 (DYNALLOC) before all this.
125 billion rows? That's 17 rows for every person on the planet! What is in this monster? |
|
Back to top |
|
 |
MikeBaker Beginner
Joined: 04 May 2004 Posts: 96 Topics: 9
|
Posted: Mon Sep 20, 2004 3:25 am Post subject: |
|
|
125 billion rows?? Obviously this must be one of your tinier databases
Seriously though, I'd recommend making sure that whoever designed this database gets to do no further design work for your shop. Undoubtedly they will continue to produce one fiasco after another. One can only pray that you are not going to end up with billions of PDS members. And as an extension of this, your overnight batch window consists of billions of jobs...  |
|
Back to top |
|
 |
shootingstar Beginner
Joined: 19 Sep 2004 Posts: 14 Topics: 11 Location: Dallas, TX
|
Posted: Tue Sep 21, 2004 7:50 pm Post subject: RE 125 billion rows |
|
|
The database in question is for tracking checking transactions for a major bank in the US. Federal law requires we keep 7 years of data and we handle between 50 and 80 million items a day. The database in question has a 28 day rolling window and a 364 week rolling window of databases (1 per day, 1 per week). The task is to automate maintenance of the DB. Either that or a couple of full-time DBAs to do the job. |
|
Back to top |
|
 |
MikeBaker Beginner
Joined: 04 May 2004 Posts: 96 Topics: 9
|
Posted: Tue Sep 21, 2004 10:01 pm Post subject: 125 billion rows |
|
|
Seven years retention of Checks is common practise. And for some IT systems you need to keep ALL historical data - even if this means 30 years worth! And processing millions of transactions per day is yet again "common practise" in many big mainframe shops. I've worked in large mainframe shops all over the world, and from experience, I can tell you, that your shop probably has the largest database in the world.  |
|
Back to top |
|
 |
Bill Dennis Advanced

Joined: 03 Dec 2002 Posts: 579 Topics: 1 Location: Iowa, USA
|
Posted: Wed Sep 22, 2004 11:26 am Post subject: |
|
|
Please excuse semigeezer.. I'm sure he means BPAM macros. There's a good discussion with examples in the DFSMS Using Data Sets manual.
You must do your own blocking of records, but it's fairly easy. Another good idea is to use ENQ/DEQ. in case users might also access the PDS via ISPF.
Regards,
Bill |
|
Back to top |
|
 |
|
|