ca.portal.admin

IDMS-DC calls to IDMS-DC sub programs

Discussion created by ca.portal.admin on Sep 9, 2005
Latest reply on Sep 14, 2005 by ca.portal.admin
Hello All:

I have an ADSO Dialog that calls an IDMS-DC COBOL program, then that
program
calls another IDMS-DC COBOL Program.

The question is this, can the IDMS-DC COBOL programs use dynamic calls or
do
they have to use static calls?

ADSO Calls
IDMS-DC Program A, then this program calls
IDMS-DC Program B

Can program A use a dynamic call to IDMS-DC Program B?

Where can I read about this in the IDMS Manuals?

Bill Allen

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








Normal

Normal
Re: IDMS R15 OS/390 to zOS
"Mike,
Look at member UMODSVC in the samplib. There are notes within the JCL to tell you what changes are needed. You or your sysprog can dynamically reload the SVC via the CAIRIM job (by default called CAS9) that loads the IDMS SVC. Here is what the CAS9 parms look like for a reload:

* ---------------------------------------------------------------------
* CAIDMS 15.0
* ---------------------------------------------------------------------
PRODUCT(CA-IDMS) VERSION(GJF0) INIT(GJF0INIT) PARM(REFRESH(SVC=243))

An important note, if you do dynamically reload the new SVC, make sure that your CV's are down and no batch is running. If you do not bring down the CV's, they will come down all by themselves (in other words, they crash).

Dan Hall

-----Original Message-----
From: IDMS 3rd-party providers forum [mailTo:IDMSVENDOR-L@LISTSERV.IUASSN.COM] On Behalf Of Mike Champagne
Sent: Sunday, September 11, 2005 5:03 PM
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM
Subject: IDMS R15 OS/390 to zOS

Our OS service provider was planning on upgrading from OS/390 2/10 to
z/OS the weekend of Labor Day. My primary task the week before was to be
researching the one task I knew (from others in this forum) that I had
to accomplish as part of this upgrade - re-linking the IDMS SVC.

Instead I was driving out of New Orleans, luckily well ahead of
Hurricane Katrina, but have been in Houston for the last two weeks since
my house is still under water and we are only starting to run jobs again
this weekend. The plant survived relatively unscathed, just some minor
wind damage to the roof.

All of my family is OK. Many of us have lost our homes, but we are all
alive, and there's something to be said for that :)

But back to IDMS & zOS . . . we went ahead with the upgrade and my mind
was elsewhere and I dropped the ball on re-linking the SVC. We stopped
batch processing on 8/31 and are just starting back up now. The CVs are
running just fine and CV-mode batch jobs are ok too. MOST local-mode
jobs are ok, but some are having problems, The workaround at this point
it just to run them in CV mode - takes a bit longer but it'll do in a
pinch.

Unfortunately, I don't have access to all the notes used when R15 was
installed (I didn't do the work and the last IDMS install I did was on
VSE anyway) and am short a lot of my own notes as well.

What job in the installation is generally the one that links the SVC?

Or, in the alternative, can someone send me JCL to link the SVC? We use
#173. I have to confess that, although a VSE SysProg for nearly twenty
years, there's a good bit about the MVS arena that I don't know. I'll
pass on to our SysProg whatever info I receive, and expect that he'll
understand what you tell me.

Thanks as always and I hope anyone else affected by this is OK as well.

There are many others certainly much much worse off than we are, and I
ask for your thoughts and prayers for them

Thanks,

Mike

PELLERIN MILNOR CORPORATION
Michel J Champagne
Systems Analyst / DBA
=20
Voice: 504-712-7589
FAX: 504-712-3589
=20
Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.
=20

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








Normal

Normal
IDMS R15 OS/390 to zOS
"Our OS service provider was planning on upgrading from OS/390 2/10 to
z/OS the weekend of Labor Day. My primary task the week before was to be
researching the one task I knew (from others in this forum) that I had
to accomplish as part of this upgrade - re-linking the IDMS SVC.

Instead I was driving out of New Orleans, luckily well ahead of
Hurricane Katrina, but have been in Houston for the last two weeks since
my house is still under water and we are only starting to run jobs again
this weekend. The plant survived relatively unscathed, just some minor
wind damage to the roof.

All of my family is OK. Many of us have lost our homes, but we are all
alive, and there's something to be said for that :)

But back to IDMS & zOS . . . we went ahead with the upgrade and my mind
was elsewhere and I dropped the ball on re-linking the SVC. We stopped
batch processing on 8/31 and are just starting back up now. The CVs are
running just fine and CV-mode batch jobs are ok too. MOST local-mode
jobs are ok, but some are having problems, The workaround at this point
it just to run them in CV mode - takes a bit longer but it'll do in a
pinch.

Unfortunately, I don't have access to all the notes used when R15 was
installed (I didn't do the work and the last IDMS install I did was on
VSE anyway) and am short a lot of my own notes as well.

What job in the installation is generally the one that links the SVC?

Or, in the alternative, can someone send me JCL to link the SVC? We use
#173. I have to confess that, although a VSE SysProg for nearly twenty
years, there's a good bit about the MVS arena that I don't know. I'll
pass on to our SysProg whatever info I receive, and expect that he'll
understand what you tell me.

Thanks as always and I hope anyone else affected by this is OK as well.

There are many others certainly much much worse off than we are, and I
ask for your thoughts and prayers for them

Thanks,

Mike

PELLERIN MILNOR CORPORATION
Michel J Champagne
Systems Analyst / DBA

Voice: 504-712-7589
FAX: 504-712-3589

Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.


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








Normal

Normal
Re: IDMS R15 OS/390 to zOS
"You can also run smp/e with

LIST LMOD(your svc) XREF as the syn and that will give you the info for
the relink as well.

Or use the umodsvc module which will probably be the easiest solution.

Dick

Richard C Borman/GIS/CSC
CSC/GIS Idms System Support
9305 Lightwave Ave
San Diego, Ca 92193-9011
office 858-573-3265
rborman@csc.com



----------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------





Mike Champagne
<mchampagne To: IDMS-L@LISTSERV.IUASSN.COM
@MILNOR.COM> cc:
Sent by: IDMS Subject: IDMS R15 OS/390 to zOS
Public
Discussion Forum
<IDMS-L


09/11/2005 02:03
PM
Please respond
to IDMS Public
Discussion Forum





Our OS service provider was planning on upgrading from OS/390 2/10 to
z/OS the weekend of Labor Day. My primary task the week before was to be
researching the one task I knew (from others in this forum) that I had
to accomplish as part of this upgrade - re-linking the IDMS SVC.

Instead I was driving out of New Orleans, luckily well ahead of
Hurricane Katrina, but have been in Houston for the last two weeks since
my house is still under water and we are only starting to run jobs again
this weekend. The plant survived relatively unscathed, just some minor
wind damage to the roof.

All of my family is OK. Many of us have lost our homes, but we are all
alive, and there's something to be said for that :)

But back to IDMS & zOS . . . we went ahead with the upgrade and my mind
was elsewhere and I dropped the ball on re-linking the SVC. We stopped
batch processing on 8/31 and are just starting back up now. The CVs are
running just fine and CV-mode batch jobs are ok too. MOST local-mode
jobs are ok, but some are having problems, The workaround at this point
it just to run them in CV mode - takes a bit longer but it'll do in a
pinch.

Unfortunately, I don't have access to all the notes used when R15 was
installed (I didn't do the work and the last IDMS install I did was on
VSE anyway) and am short a lot of my own notes as well.

What job in the installation is generally the one that links the SVC?

Or, in the alternative, can someone send me JCL to link the SVC? We use
#173. I have to confess that, although a VSE SysProg for nearly twenty
years, there's a good bit about the MVS arena that I don't know. I'll
pass on to our SysProg whatever info I receive, and expect that he'll
understand what you tell me.

Thanks as always and I hope anyone else affected by this is OK as well.

There are many others certainly much much worse off than we are, and I
ask for your thoughts and prayers for them

Thanks,

Mike

PELLERIN MILNOR CORPORATION
Michel J Champagne
Systems Analyst / DBA

Voice: 504-712-7589
FAX: 504-712-3589

Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.

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








Normal

Normal
Re: IDMS R15 OS/390 to zOS
"SMPE SVC JCL for 15.0



//IGC211 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD *
#SVCOPT , X
SVCNO=211, X
SVCXLEN=0, X
ENVIRON=MVS, X
CVKEY=, X
SMF=YES
END
//SYSUT2 DD DSN=XXXXX.SMPE.PPOPTION(SVC211), <===
// DISP=OLD
/*
//*
//*-------------------------------------------------------------------*
//* RECEIVE AND APPLY CHECK *
//*-------------------------------------------------------------------*
//RECEIVE EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U'
//SMPCSI DD DISP=SHR,DSN=XXXXX.SMPE.CSI
//SMPHOLD DD DUMMY
//SMPPTFIN DD DATA,DLM='%%'
++USERMOD(USVC211).
++VER(Z038) FMID(CGJF005).
++JCLIN /***************************************/
/* DO NOT CHANGE EITHER OF THE DD */
/* STATEMENTS AND DO NOT CHANGE */
/* 'DISTLOAD' ON THE INCLUDE STATE- */
/* MENTS. */
/***************************************/.
//LNKNRMT EXEC PGM=IEWL,PARM='LET,MAP,LIST,NCAL'
//DISTLOAD DD DSN=DO.NOT.CHANGE.DISTLOAD,DISP=SHR
//SYSLMOD DD DSN=DO.NOT.CHANGE.APFLIB,DISP=SHR
//SYSLIN DD *
INCLUDE DISTLOAD(SVC211)
INCLUDE DISTLOAD(IDMSMSVC)
ENTRY IGC211
NAME IGC211(R)
/*
++SRC(SVC211) DISTLIB(DISTSRC) DISTMOD(DISTLOAD) TXLIB(PPOPTION).
%%
//SMPCNTL DD *
SET BOUNDARY(GLOBAL).
RECEIVE SELECT(USVC211).
SET BOUNDARY(IDMSTGT).
APPLY CHECK SELECT(USVC211).
/*
//*-------------------------------------------------------------------*
//* APPLY *
//*-------------------------------------------------------------------*
//APPLY EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U',COND=(0,LT)
//SMPCSI DD DISP=SHR,DSN=XXXXX.SMPE.CSI
//SMPCNTL DD *
SET BOUNDARY(IDMSTGT).
APPLY SELECT(USVC211).
/*
//



Christopher W. Angerer
State of Missouri / OA / ITSD
Computer Information Technology Specialist I
mailTo:Chris.Angerer@oa.mo.gov
(573) 751-1029
IMPROVE: Change may bring IMPROVEMENT.....
but IMPROVEMENT always brings change.

Outcomes