ca.portal.admin

Re:more on SVC

Discussion created by ca.portal.admin on May 7, 2009
CA changed to the doc for r 17 - when running 2 releases of IDMS on the
same SVC (which requires the refresh option):

The doc is correct. You should always use the latest GJxxINIT module and
the latest SVC, which are downward compatible.
The two CAIRIM statements are needed so that both releases are
registered to use the indicated SVC.

so if running 16 and 17 on the same SVC - use the 17 svc AND init module
to init both the R16 and R17 CVs .....



Chris Hoelscher
Senior IDMS & DB2 Database Administrator Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly




The information transmitted is intended only for the person or entity to
which it is addressed and may contain CONFIDENTIAL material. If you
receive this material/information in error, please contact the sender
and delete or destroy the material/information.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: more on SVC
"WEll I would not want to - but if your shop says ""IDMS gets SVC173 -
have fun"" - then you do not have much of a choice -

luckily - i set up a separate SVCs for SANDBOX, TEST, QA, and PROD - so we
have not had to deal with this recently


Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly





The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] more on SVC
"WEll I would not want to - but if your shop says ""IDMS gets SVC173 -
have fun"" - then you do not have much of a choice -

luckily - i set up a separate SVCs for SANDBOX, TEST, QA, and PROD - so we
have not had to deal with this recently


Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly





The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Replacing an element in a record
"I have a simple question and I know all you experts can help me.

I have a record that is composed of 3 main data elements each consisting
of subordinate elements. A subordinate element is being changed in one
of the main data elements.

Normally, I change the record to a higher version number, create a new
version 1 record, recompile the schema with the new record version 1,
and then recompile all the programs that use this record so they are all
using the same record definition. It is a lot of work but then I know
every program is using the same record definition.

In the interest of speed, it was decided not to recompile all the
programs since they will not use the new fields (the system is being
replaced in the next 2-3 years, unfortunately not using IDMS :-( ) The
part of the record being changed is defined as filler and is all spaces.
The new elements are all alphanumeric so I do not have to initialize
them. But how do I get the record to recognize the changed subordinate
element without going through schema and program compiles? I cannot
simply replace the record as it is in a schema and so is owned by the
schema compiler. Is there a way to get around this?

We are running V16.0 SP7.

Thanks for your help.
Petra
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Replacing an element in a record
"I have a simple question and I know all you experts can help me.

I have a record that is composed of 3 main data elements each consisting
of subordinate elements. A subordinate element is being changed in one
of the main data elements.

Normally, I change the record to a higher version number, create a new
version 1 record, recompile the schema with the new record version 1,
and then recompile all the programs that use this record so they are all
using the same record definition. It is a lot of work but then I know
every program is using the same record definition.

In the interest of speed, it was decided not to recompile all the
programs since they will not use the new fields (the system is being
replaced in the next 2-3 years, unfortunately not using IDMS :-( ) The
part of the record being changed is defined as filler and is all spaces.
The new elements are all alphanumeric so I do not have to initialize
them. But how do I get the record to recognize the changed subordinate
element without going through schema and program compiles? I cannot
simply replace the record as it is in a schema and so is owned by the
schema compiler. Is there a way to get around this?

We are running V16.0 SP7.

Thanks for your help.
Petra
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Replacing an element in a record
"PLAN A

assume existing record is v 1.

a) create v 2 of the record with the desired changes

b)

MOD
SCHEMA NAME IS ssssssss VERSION IS 1
MOD
RECORD NAME IS xxxxxxxx
SHARE STRUCTURE OF RECORD SG-PROS VERSION 2
.
VALIDATE.

MOD REC xxxxxxxx v 1 new version is 99.
MOD REC xxxxxxxx v 2 new version is 1.


MOD SCHEMA ssssssss. VERSION IS 1. VALIDATE. REG AFF SUBSC.

PLAN B:
or - create a work-record with the new layout and include in the programs
that need the new data

after an obtain - move the schema record contents to the work-record and
process from there
before a store or modify - move the work record contents to the schema
record

Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly




The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Replacing an element in a record
"PLAN A

assume existing record is v 1.

a) create v 2 of the record with the desired changes

b)

MOD
SCHEMA NAME IS ssssssss VERSION IS 1
MOD
RECORD NAME IS xxxxxxxx
SHARE STRUCTURE OF RECORD SG-PROS VERSION 2
.
VALIDATE.

MOD REC xxxxxxxx v 1 new version is 99.
MOD REC xxxxxxxx v 2 new version is 1.


MOD SCHEMA ssssssss. VERSION IS 1. VALIDATE. REG AFF SUBSC.

PLAN B:
or - create a work-record with the new layout and include in the programs
that need the new data

after an obtain - move the schema record contents to the work-record and
process from there
before a store or modify - move the work record contents to the schema
record

Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly




The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Replacing an element in a record
"Well,

I think you can do it.
Create a new version of the record - same layout, then add that version to
the schema.
Change version 1 to the new layout, that is the one used by the programs,
but no longer by the schema.
Then change the schema once again to use version 1 and recompile the
subschemas.

You lose control of which programs recognize the new layout, but I guess
that is what you were looking for.

I have not tested this, but in theory it should work.

As Yogi Berra said, ""In theory there is no difference between theory and
practice. In practice there is.""

Tommy Petersen
110 Cokesbury Rd
Room 542H
Lebanon, NJ 08833

Phone:
Internal 200 - 3699
External (908) 236-3699
Fax: (908) 236-3692




Petra LaFrese
<lafresep@U.ARIZO
NA.EDU> To
Sent by: IDMS IDMS-L@LISTSERV.IUASSN.COM
Public Discussion cc
Forum
<IDMS-L@LISTSERV. Subject
IUASSN.COM> Replacing an element in a record


05/07/2009 08:23
PM


Please respond to
lafresep@u.arizon
a.edu






I have a simple question and I know all you experts can help me.

I have a record that is composed of 3 main data elements each consisting
of subordinate elements. A subordinate element is being changed in one
of the main data elements.

Normally, I change the record to a higher version number, create a new
version 1 record, recompile the schema with the new record version 1,
and then recompile all the programs that use this record so they are all
using the same record definition. It is a lot of work but then I know
every program is using the same record definition.

In the interest of speed, it was decided not to recompile all the
programs since they will not use the new fields (the system is being
replaced in the next 2-3 years, unfortunately not using IDMS :-( ) The
part of the record being changed is defined as filler and is all spaces.
The new elements are all alphanumeric so I do not have to initialize
them. But how do I get the record to recognize the changed subordinate
element without going through schema and program compiles? I cannot
simply replace the record as it is in a schema and so is owned by the
schema compiler. Is there a way to get around this?

We are running V16.0 SP7.

Thanks for your help.
Petra
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Replacing an element in a record
"Well,

I think you can do it.
Create a new version of the record - same layout, then add that version to
the schema.
Change version 1 to the new layout, that is the one used by the programs,
but no longer by the schema.
Then change the schema once again to use version 1 and recompile the
subschemas.

You lose control of which programs recognize the new layout, but I guess
that is what you were looking for.

I have not tested this, but in theory it should work.

As Yogi Berra said, ""In theory there is no difference between theory and
practice. In practice there is.""

Tommy Petersen
110 Cokesbury Rd
Room 542H
Lebanon, NJ 08833

Phone:
Internal 200 - 3699
External (908) 236-3699
Fax: (908) 236-3692




Petra LaFrese
<lafresep@U.ARIZO
NA.EDU> To
Sent by: IDMS IDMS-L@LISTSERV.IUASSN.COM
Public Discussion cc
Forum
<IDMS-L@LISTSERV. Subject
IUASSN.COM> Replacing an element in a record


05/07/2009 08:23
PM


Please respond to
lafresep@u.arizon
a.edu






I have a simple question and I know all you experts can help me.

I have a record that is composed of 3 main data elements each consisting
of subordinate elements. A subordinate element is being changed in one
of the main data elements.

Normally, I change the record to a higher version number, create a new
version 1 record, recompile the schema with the new record version 1,
and then recompile all the programs that use this record so they are all
using the same record definition. It is a lot of work but then I know
every program is using the same record definition.

In the interest of speed, it was decided not to recompile all the
programs since they will not use the new fields (the system is being
replaced in the next 2-3 years, unfortunately not using IDMS :-( ) The
part of the record being changed is defined as filler and is all spaces.
The new elements are all alphanumeric so I do not have to initialize
them. But how do I get the record to recognize the changed subordinate
element without going through schema and program compiles? I cannot
simply replace the record as it is in a schema and so is owned by the
schema compiler. Is there a way to get around this?

We are running V16.0 SP7.

Thanks for your help.
Petra
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Replacing an element in a record
"Tommy's version of the events are bang on and are similar to what we routin=
ely do.

More importantly this method allows you to preserve IDD statistics associat=
ed with the programs, schemas and subschemas. What we sometimes do is to a=
ssociate the new subordinate element with the newly ""copied"" record to prov=
e that the new format works.

Once the schema is associated with the ""copied"" record, you can now modify =
the original record with the new subordinate element. Then reassociate the=
schema with the original record (version 1). Validate the schema, regener=
ate the affected subschemas.=20=20=20

Given your situation, all that's left is to recompile the programs that nee=
d to exploit the new subordinate elements. All other programs can be left =
uncompiled/unmodified as they do not exploit the new subordinate elements.

Thanks,
Brian Lee
DBA
Pacific Blue Cross.

Outcomes