ca.portal.admin

A ""complete"" cobol program

Discussion created by ca.portal.admin on Jun 30, 2006
Latest reply on Jun 30, 2006 by ca.portal.admin
Hi listers:
I need a way for a cobol program to be able to access a subschema,
records, sets, etc...
simply buy a parm statement on the execute jcl statement (or another
way if possible).

We would like to have 1 program that ""does it all"".
In other words if I access SS-a, sets-a and recs-a, with a batch job,
is there a way to do the same, to access SS-b, sets-b and recs-b
by a simple change such as just changing parms on the execute
statement on the jcl or if there's a better idea please share.

I lack the expertise to do this and was wondering if anyone out there
has an idea.

Thanks for your time.
Wayne




J. Wayne Doneker
BAE Systems
York Pa.
717 225 8109
Email: john.doneker@baesystems.com

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"Re: A ""complete"" cobol program"
"Wayne - Why does your email say John?

My thought would be to write a called COBOL program for each subschema -
like a stored procedure - and then have a calling program use the PARM
to determine which program to call.


----- Original message -----
From: ""John Doneker"" <John.Doneker@BAESYSTEMS.COM>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Fri, 30 Jun 2006 07:54:13 -0500
Subject: A ""complete"" cobol program

Hi listers:
I need a way for a cobol program to be able to access a subschema,
records, sets, etc...
simply buy a parm statement on the execute jcl statement (or another
way if possible).

We would like to have 1 program that ""does it all"".
In other words if I access SS-a, sets-a and recs-a, with a batch job,
is there a way to do the same, to access SS-b, sets-b and recs-b
by a simple change such as just changing parms on the execute
statement on the jcl or if there's a better idea please share.

I lack the expertise to do this and was wondering if anyone out there
has an idea.

Thanks for your time.
Wayne




J. Wayne Doneker
BAE Systems
York Pa.
717 225 8109
Email: john.doneker@baesystems.com

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"Re: A ""complete"" cobol program"
"John

my first thought (not always the best, admittedly) is to write a
program that does what you want for a specific subschema, then
precompile it - look at how the program treated the subschema
invocation, obtains for the sets and records - and then, in the
intermediate version, modify the code to pass variables into the
CALL IDMS ... syntax, rather than the hard coded values you
originally coded. - supplying the values from a parm on the exec, or
via sysin DD *, or whatever

then compile and link-edit

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"A ""complete"" cobol program"
"Hi listers:
I need a way for a cobol program to be able to access a subschema,
records, sets, etc...
simply buy a parm statement on the execute jcl statement (or another
way if possible).

We would like to have 1 program that ""does it all"".
In other words if I access SS-a, sets-a and recs-a, with a batch job,
is there a way to do the same, to access SS-b, sets-b and recs-b
by a simple change such as just changing parms on the execute
statement on the jcl or if there's a better idea please share.

I lack the expertise to do this and was wondering if anyone out there
has an idea.

Thanks for your time.
Wayne




J. Wayne Doneker
BAE Systems
York Pa.
717 225 8109
Email: john.doneker@baesystems.com

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"Re: A ""complete"" cobol program"
"Thanks Cindy, actually I do not have to change subschemas. I can use a
global subschema.
Thanks again for your reply.

J. Wayne Doneker
BAE Systems
York Pa.
717 225 8109
Email: john.doneker@baesystems.com

cakask@AOL.COM 6/30/2006 10:00:00 AM >>>
this may be a dumb thought - it has been years since I have done
serious IDMS dictionary work and don't have access to IDMS or a copy of
the network subschema (IDMSNWKA?)

But I recall using the network subschema to access info - I
specifically remember getting (actual) queue records - is the
information you are looking for available there?

Cindy Kline

Outcomes