[IDMS-L] finding all OBTAINING USING .....

[ca.portal.admin]

when migrating from 15 to 17 (might have also happened had me migrated
to
16) - we noted that all subsequent of cobol code ""OBTAIN .... USING""
now
requires a terminating period or semicolon (to enforce only one
character
string to be interpreted as the sort-key element name. we have
addressed
this as each program was compiled when a change is made.

we recently picked up a 3rd party productivity tool (i am really not
sure
which one) - and our developers want to compile EVERY program abd are
complaining about the number of precompiles failing due to this issue -
and want all such programs pre-identified

has anyone written a program/script to examine program source
repositories
looking for OBTAIN...USING .... DML? (and more importantly, willing to
share?)

thanks,
Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
FW: [IDMS-L] finding all OBTAINING USING .....
"Hi Chris - I don't have a utility to scan the source but I did write an
apar (TB99850) to help out with this situation.

The apar first changes the generic DML004 message issued in this case to
a more descriptive DML084. With the apar applied and optional bit
settings, you can control the severity of the DML084. This will allow
precompiles complete with a warning or successful return code. As you
have done, we strongly suggest that the programs are addressed and
corrected as encountered to add the terminator the OBTAIN USING DML.
However we have found situations like yours where it is helpful to not
have a hard error for this situation. Changing the severity to a
warning will allow the precompile step to complete but warn you that the
situation in the program needs to be addressed. Remember if FIND/OBTAIN
USING DML statement is not coded properly runtime errors can occur.

The apar can be requested by opening an issue with Technical Support.
It has not been officially published yet.

Thanks, Carla


Carla Pereira
CA
Sr Sustaining Engineer
Tel: [phone]
Fax: [phone]
[e-mail]

[ca.portal.admin]

when migrating from 15 to 17 (might have also happened had me migrated to 1=
6) - we noted that all subsequent of cobol code ""OBTAIN .... USING"" now re=
quires a terminating period or semicolon (to enforce only one character str=
ing to be interpreted as the sort-key element name. we have addressed this=
as each program was compiled when a change is made.

we recently picked up a 3rd party productivity tool (i am really not sure w=
hich one) - and our developers want to compile EVERY program abd are compla=
ining about the number of precompiles failing due to this issue - and want =
all such programs pre-identified

has anyone written a program/script to examine program source repositories =
looking for OBTAIN...USING .... DML? (and more importantly, willing to shar=
e?)

thanks,
Chris Hoelscher
Senior IDMS & DB2 Database Administrator Humana Inc
502-476-2538
[e-mail]

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 wh=
ich 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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=
~~~~~~~<end paste>~~~~~~~~~~~~~~~~~~~~~~~~~

Gary Cherlet
Justice Technology Services
Department of Justice, SA Government
Telephone [phone]
Facsimile [phone]
Mobile [phone]
MailTo:[e-mail]

This e-mail message and any attachments are qualified as follows: Addressin=
g: If you have received this e-mail in error, please advise by reply e-mai=
l to the sender. Please also destroy the original transmission and its con=
tents. Confidentiality: This e-mail may contain confidential information w=
hich also may be legally privileged. Only the intended recipient(s) may ac=
cess, use, distribute or copy this e-mail. Individual Views: Unless otherw=
ise indicated, the views expressed are those of the sender, not Justice Tec=
hnology Services. Computer Viruses: It is the recipient's responsibility t=
o check the e-mail and any attached files for viruses.

[ca.portal.admin]

when migrating from 15 to 17 (might have also happened had me migrated to 16) - we noted that all subsequent of cobol code ""OBTAIN .... USING"" now requires a terminating period or semicolon (to enforce only one character string to be interpreted as the sort-key element name. we have addressed this as each program was compiled when a change is made.

we recently picked up a 3rd party productivity tool (i am really not sure which one) - and our developers want to compile EVERY program abd are complaining about the number of precompiles failing due to this issue - and want all such programs pre-identified

has anyone written a program/script to examine program source repositories looking for OBTAIN...USING .... DML? (and more importantly, willing to share?)

thanks,
Chris Hoelscher
Senior IDMS & DB2 Database Administrator Humana Inc
502-476-2538
[e-mail]

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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<end paste>~~~~~~~~~~~~~~~~~~~~~~~~~

Gary Cherlet
Justice Technology Services
Department of Justice, SA Government
Telephone [phone]
Facsimile [phone]
Mobile [phone]
MailTo:[e-mail]

This e-mail message and any attachments are qualified as follows: Addressing: If you have received this e-mail in error, please advise by reply e-mail to the sender. Please also destroy the original transmission and its contents. Confidentiality: This e-mail may contain confidential information which also may be legally privileged. Only the intended recipient(s) may access, use, distribute or copy this e-mail. Individual Views: Unless otherwise indicated, the views expressed are those of the sender, not Justice Technology Services. Computer Viruses: It is the recipient's responsibility to check the e-mail and any attached files for viruses.

[ca.portal.admin]

when migrating from 15 to 17 (might have also happened had me migrated
to
16) - we noted that all subsequent of cobol code ""OBTAIN .... USING""
now
requires a terminating period or semicolon (to enforce only one
character
string to be interpreted as the sort-key element name. we have
addressed
this as each program was compiled when a change is made.

we recently picked up a 3rd party productivity tool (i am really not
sure
which one) - and our developers want to compile EVERY program abd are
complaining about the number of precompiles failing due to this issue -
and want all such programs pre-identified

has anyone written a program/script to examine program source
repositories
looking for OBTAIN...USING .... DML? (and more importantly, willing to
share?)

thanks,
Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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.



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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
JVM
"Has anyone attempted to get a JVM running under IDMS-DC? Have you been successfull? I know that there is a version that runs under CICS 2.3.

Tia,

Bob

Bob Wiklund
Tiburon Technologies
623 594-6022
"
IDMS Public Discussion Forum
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
using IBM Health checker w/CA-IDMS
"with PTF RO12080, IDMS (R17 SP1) now exploits the IBM Health Checker.
Ignorant soul that I am, I had never heard of the facility - so i did a
little digging around:

IDMS now sets some baselines for what is ""best practice"" or ""acceptable""
for a CV - tests those conditions, and writes the results to a centralized
repository, as well as displaying an abbreviated version on the CV jeslog
itself

this looks interesting - so I thought I would share what little I picked
up .....


this JCL:

//your jobcard
//HZSPRINT EXEC PGM=HZSPRNT,TIME=1440,REGION=0M,
// PARM=('CHECK(CA_IDMS,*)')
//SYSOUT DD SYSOUT=X,LRECL=256

will dump the repository for ALL idms CVs (at least on that LPAR, I do not
know if it would pick up for all CVs in the 'plex)

the output looks like this:

************************************************************************
* *
* HZSPRINT (HBB7750-07288) 2009/11/05 15:40 *
* *
* HZSU001I Check messages *
* Sysplex: PLEX1 System: SYST *
* *
* Filter: CHECK(CA_IDMS,*) *
* *
************************************************************************



************************************************************************
* *
* Start: CHECK(CA_IDMS,IDMS_SCRATCH_IN_MEMORY@SYST0023) *
* *
************************************************************************

CHECK(CA_IDMS,IDMS_SCRATCH_IN_MEMORY@SYST0023)
START TIME: 11/05/2009 14:38:10.268692
CHECK DATE: 20091008 CHECK SEVERITY: MEDIUM

DC045000 The scratch area is maintained in memory according to CA IDMS
best practices. CA IDMS scratch performance is optimal.

END TIME: 11/05/2009 14:38:10.276808 STATUS: SUCCESSFUL

************************************************************************
* *
* End: CHECK(CA_IDMS,IDMS_SCRATCH_IN_MEMORY@SYST0023) *
* *
************************************************************************



*************************************************************************
*
* Start: CHECK(CA_IDMS,IDMS_ZIIP_USAGE@SYST0023) *
* *
************************************************************************

CHECK(CA_IDMS,IDMS_ZIIP_USAGE@SYST0023)
START TIME: 11/05/2009 14:38:10.268638
CHECK DATE: 20091008 CHECK SEVERITY: MEDIUM

DC016107 The zIIP processor option for CA IDMS system SYST0023 is
properly configured for the current hardware configuration.

END TIME: 11/05/2009 14:38:10.276700 STATUS: SUCCESSFUL

************************************************************************
* *
* End: CHECK(CA_IDMS,IDMS_ZIIP_USAGE@SYST0023) *
* *
************************************************************************



************************************************************************
* *
* Start: CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS@SYST0023) *
* *
************************************************************************

CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS@SYST0023)
START TIME: 11/05/2009 15:38:10.275267
CHECK DATE: 20091008 CHECK SEVERITY: HIGH
CHECK PARM: CPURATIO(90)


DC285900 CPU effectiveness 100% for this interval is within the
acceptable range.

END TIME: 11/05/2009 15:38:10.275453 STATUS: SUCCESSFUL

************************************************************************
* *
* End: CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS@SYST0023) *
* *
************************************************************************



************************************************************************
* *
* Start: CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST0023) *
* *
************************************************************************

CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST0023)
START TIME: 11/05/2009 14:38:10.266378
CHECK DATE: 20091008 CHECK SEVERITY: MEDIUM

* Medium Severity Exception *

DC200025 Change Tracking of the CA IDMS system SYST0023 is disabled
because no SYSTRK file is allocated or referenced in the Central Version
(CV) startup JCL. Manual intervention may be required in case of CV
failure.

It is strongly recommended that Change Tracking be enabled. Change
Tracking permits changing the database environment of a CV in a
fault-tolerant manner. If the CV fails, the runtime database definition
is restored from SYSTRK files during restart, ensuring that the files
being updated at the time of failure are the ones recovered by
warmstart.

Explanation: A SYSTRK file contains a description of the database
environment most recently in use by the CV. During startup, an image
of the current Device Media Control Language module (DMCL) is
written to SYSTRK along with information about database and journal
files defined in the JCL.

If no SYSTRK file is referenced in the execution JCL of the CV,
Change Tracking is not in effect, meaning that the potential for a
warmstart failure is introduced when varying in a new copy of a DMCL
or dynamically changing the data set name of a file. Additionally,
any permanent status established for an area whose page range is
changed is lost or may be misapplied to another area whose page
range is also changed.

System Action: CA IDMS continues processing, however manual
intervention may be required in case of CV failure.

Operator Response: Report this status to the CA IDMS Database
Administrator.

System Programmer Response: To implement Change Tracking for a CV,
take the following steps:

1. Create a model SYSTRK file whose dataset name establishes the
pattern for the individual SYSTRK files.

2. Create and format two to four SYSTRK files whose dataset names
are the same as that of the model SYSTRK file suffixed with a unique
digit from 1 to 9. A minimum of two SYSTRK files are required due to
internal mirroring which is used to provide fault tolerance and
recoverability in case of file damage.

3. Alter the CV execution JCL to reference the model SYSTRK file.
Use a DDname established by the SYSIDMS parameter
SYSTRK_DDNAME_PREFIX. The default value for this parameter is
SYSTRK.

The current SYSIDMS file is:
IDMS.DBA.HUMANA.LOADLIB on volume DDBD18

SYSIDMS is a parameter file added to the JCL stream of batch jobs
running in local mode or under CV.

4. Alter the JCL for the associated archive journal job to also
reference the model SYSTRK file and to remove references to the disk
journal files.

5. Optionally, change the JCL of other local mode jobs to reference
the model SYSTRK file and remove explicit references to database
files.

Problem Determination: N/A

Source: CA IDMS

Reference Documentation: Refer to CA IDMS System Operations Guide,
topic ""Change Tracking"".

For more information about sizing and formatting SYSTRK files, refer
to CA IDMS Utilities Guide, topic ""FORMAT utility statement"".

For more information about managing Change Tracking, refer to CA
IDMS System Tasks and Operator Commands Guide, topic ""DCMT DISPLAY
CHANGE TRACKING"" and ""DCMT VARY CHANGE TRACKING"".

Automation: Send an e-mail reporting this status to the CA IDMS
Database Administrator.

Check Reason: Verify whether CA IDMS Change Tracking is enabled.

END TIME: 11/05/2009 14:38:10.276345 STATUS: EXCEPTION-MED

************************************************************************
* *
* End: CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST0023) *
* *
************************************************************************


Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
using IBM Health checker w/CA-IDMS
"with PTF RO12080, IDMS (R17 SP1) now exploits the IBM Health Checker.
Ignorant soul that I am, I had never heard of the facility - so i did a
little digging around:

IDMS now sets some baselines for what is ""best practice"" or ""acceptable""
for a CV - tests those conditions, and writes the results to a centralized
repository, as well as displaying an abbreviated version on the CV jeslog
itself

this looks interesting - so I thought I would share what little I picked
up .....


this JCL:

//your jobcard
//HZSPRINT EXEC PGM=HZSPRNT,TIME=1440,REGION=0M,
// PARM=('CHECK(CA_IDMS,*)')
//SYSOUT DD SYSOUT=X,LRECL=256

will dump the repository for ALL idms CVs (at least on that LPAR, I do not
know if it would pick up for all CVs in the 'plex)

the output looks like this:

************************************************************************
* *
* HZSPRINT (HBB7750-07288) 2009/11/05 15:40 *
* *
* HZSU001I Check messages *
* Sysplex: PLEX1 System: SYST *
* *
* Filter: CHECK(CA_IDMS,*) *
* *
************************************************************************



************************************************************************
* *
* Start: CHECK(CA_IDMS,IDMS_SCRATCH_IN_MEMORY@SYST0023) *
* *
************************************************************************

CHECK(CA_IDMS,IDMS_SCRATCH_IN_MEMORY@SYST0023)
START TIME: 11/05/2009 14:38:10.268692
CHECK DATE: 20091008 CHECK SEVERITY: MEDIUM

DC045000 The scratch area is maintained in memory according to CA IDMS
best practices. CA IDMS scratch performance is optimal.

END TIME: 11/05/2009 14:38:10.276808 STATUS: SUCCESSFUL

************************************************************************
* *
* End: CHECK(CA_IDMS,IDMS_SCRATCH_IN_MEMORY@SYST0023) *
* *
************************************************************************



*************************************************************************
*
* Start: CHECK(CA_IDMS,IDMS_ZIIP_USAGE@SYST0023) *
* *
************************************************************************

CHECK(CA_IDMS,IDMS_ZIIP_USAGE@SYST0023)
START TIME: 11/05/2009 14:38:10.268638
CHECK DATE: 20091008 CHECK SEVERITY: MEDIUM

DC016107 The zIIP processor option for CA IDMS system SYST0023 is
properly configured for the current hardware configuration.

END TIME: 11/05/2009 14:38:10.276700 STATUS: SUCCESSFUL

************************************************************************
* *
* End: CHECK(CA_IDMS,IDMS_ZIIP_USAGE@SYST0023) *
* *
************************************************************************



************************************************************************
* *
* Start: CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS@SYST0023) *
* *
************************************************************************

CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS@SYST0023)
START TIME: 11/05/2009 15:38:10.275267
CHECK DATE: 20091008 CHECK SEVERITY: HIGH
CHECK PARM: CPURATIO(90)


DC285900 CPU effectiveness 100% for this interval is within the
acceptable range.

END TIME: 11/05/2009 15:38:10.275453 STATUS: SUCCESSFUL

************************************************************************
* *
* End: CHECK(CA_IDMS,IDMS_CPU_EFFECTIVENESS@SYST0023) *
* *
************************************************************************



************************************************************************
* *
* Start: CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST0023) *
* *
************************************************************************

CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST0023)
START TIME: 11/05/2009 14:38:10.266378
CHECK DATE: 20091008 CHECK SEVERITY: MEDIUM

* Medium Severity Exception *

DC200025 Change Tracking of the CA IDMS system SYST0023 is disabled
because no SYSTRK file is allocated or referenced in the Central Version
(CV) startup JCL. Manual intervention may be required in case of CV
failure.

It is strongly recommended that Change Tracking be enabled. Change
Tracking permits changing the database environment of a CV in a
fault-tolerant manner. If the CV fails, the runtime database definition
is restored from SYSTRK files during restart, ensuring that the files
being updated at the time of failure are the ones recovered by
warmstart.

Explanation: A SYSTRK file contains a description of the database
environment most recently in use by the CV. During startup, an image
of the current Device Media Control Language module (DMCL) is
written to SYSTRK along with information about database and journal
files defined in the JCL.

If no SYSTRK file is referenced in the execution JCL of the CV,
Change Tracking is not in effect, meaning that the potential for a
warmstart failure is introduced when varying in a new copy of a DMCL
or dynamically changing the data set name of a file. Additionally,
any permanent status established for an area whose page range is
changed is lost or may be misapplied to another area whose page
range is also changed.

System Action: CA IDMS continues processing, however manual
intervention may be required in case of CV failure.

Operator Response: Report this status to the CA IDMS Database
Administrator.

System Programmer Response: To implement Change Tracking for a CV,
take the following steps:

1. Create a model SYSTRK file whose dataset name establishes the
pattern for the individual SYSTRK files.

2. Create and format two to four SYSTRK files whose dataset names
are the same as that of the model SYSTRK file suffixed with a unique
digit from 1 to 9. A minimum of two SYSTRK files are required due to
internal mirroring which is used to provide fault tolerance and
recoverability in case of file damage.

3. Alter the CV execution JCL to reference the model SYSTRK file.
Use a DDname established by the SYSIDMS parameter
SYSTRK_DDNAME_PREFIX. The default value for this parameter is
SYSTRK.

The current SYSIDMS file is:
IDMS.DBA.HUMANA.LOADLIB on volume DDBD18

SYSIDMS is a parameter file added to the JCL stream of batch jobs
running in local mode or under CV.

4. Alter the JCL for the associated archive journal job to also
reference the model SYSTRK file and to remove references to the disk
journal files.

5. Optionally, change the JCL of other local mode jobs to reference
the model SYSTRK file and remove explicit references to database
files.

Problem Determination: N/A

Source: CA IDMS

Reference Documentation: Refer to CA IDMS System Operations Guide,
topic ""Change Tracking"".

For more information about sizing and formatting SYSTRK files, refer
to CA IDMS Utilities Guide, topic ""FORMAT utility statement"".

For more information about managing Change Tracking, refer to CA
IDMS System Tasks and Operator Commands Guide, topic ""DCMT DISPLAY
CHANGE TRACKING"" and ""DCMT VARY CHANGE TRACKING"".

Automation: Send an e-mail reporting this status to the CA IDMS
Database Administrator.

Check Reason: Verify whether CA IDMS Change Tracking is enabled.

END TIME: 11/05/2009 14:38:10.276345 STATUS: EXCEPTION-MED

************************************************************************
* *
* End: CHECK(CA_IDMS,IDMS_CHANGE_TRACKING@SYST0023) *
* *
************************************************************************


Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Second Data Center for Disaster Recovery
"Dear Listers :

We will be opening a new Disaster Recovery Center in less than a year.=20
We will be replicating all data to this center from our primary =
operations using an IBM product called=20
""Global Mirror"".=20

All data is replicated at the DASD block level in real time for all =
volumes.

The primary and secondary sites are not expected to be more than a =
minute or=20
two out-of-sync during the heaviest of processing.=20

All our archive journals are written to disk and then migrated off to =
tape=20
after several days.=20

Also, every day, we do a FLASHCOPY of the entire mainframe complex and =
do=20
nightly tape backups of the Flashed volumes.
This also captures all database, disk journals, and journal archives.=20

With all databases, journals, and even journal archives on disk...=20
and
In a true disaster, it seems that recovery is as simple as starting an =
instance of IDMS at the DR site and=20
let it go through WARMSTART.=20

Am I correct about this, or is it more complicated than that?=20
And if more complicated, I'll have the archives replicated if I have to =
do more.

Thanks.=20
Jon Gocher=20
"
IDMS 3rd-party providers forum
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Second Data Center for Disaster Recovery
"Dear Listers :

We will be opening a new Disaster Recovery Center in less than a year.
We will be replicating all data to this center from our primary operations using an IBM product called
""Global Mirror"".

All data is replicated at the DASD block level in real time for all volumes.

The primary and secondary sites are not expected to be more than a minute or
two out-of-sync during the heaviest of processing.

All our archive journals are written to disk and then migrated off to tape
after several days.

Also, every day, we do a FLASHCOPY of the entire mainframe complex and do
nightly tape backups of the Flashed volumes.
This also captures all database, disk journals, and journal archives.

With all databases, journals, and even journal archives on disk...
and
In a true disaster, it seems that recovery is as simple as starting an instance of IDMS at the DR site and
let it go through WARMSTART.

Am I correct about this, or is it more complicated than that?
And if more complicated, I'll have the archives replicated if I have to do more.

Thanks.
Jon Gocher
"
IDMS Public Discussion Forum
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Re: Second Data Center for Disaster Recovery
"Yes it is - we use PPRC (possibly the same product) - assuming that all volumes were replicated (an early problem) all you really need to do is start the CVs

Sent via BlackBerry by AT&T

[ca.portal.admin]

when migrating from 15 to 17 (might have also happened had me migrated
to
16) - we noted that all subsequent of cobol code ""OBTAIN .... USING""
now
requires a terminating period or semicolon (to enforce only one
character
string to be interpreted as the sort-key element name. we have
addressed
this as each program was compiled when a change is made.

we recently picked up a 3rd party productivity tool (i am really not
sure
which one) - and our developers want to compile EVERY program abd are
complaining about the number of precompiles failing due to this issue -
and want all such programs pre-identified

has anyone written a program/script to examine program source
repositories
looking for OBTAIN...USING .... DML? (and more importantly, willing to
share?)

thanks,
Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
IDMS Webcast
" The next CA IDMS Technical Webcast is Tuesday September 22, 2009 at 11 AM ET, titled Maintaining Your CA IDMS Software Using CA Mainframe Software Manager.

CA Mainframe Software Manager (MSM) is now available for CA IDMS maintenance. In this webcast, we will discuss these new capabilities, improvements to CA IDMS r17 PTF delivery and how you can get started using CA MSM to manage your CA IDMS software environment.

See ca.com/idms<http://ca.com/idms> or go directly to http://www.ca.com/us/events/item.aspx?e=215635&eis=1 to register.
"
IDMS Public Discussion Forum
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Backward Migration from 16 to 15
"Hello All:



Last weekend I took two clients to IDMS Release 16.0 SP7 from 15.0 SP2 and
SP7.



Both Client sites have successfully backward migrated ADS/O dialogs with
changes and without changes.



I applied Optional APAR 251 to each IDMS 16.0 SP7 system and it worked like
a charm.



I am very grateful to Mr. Thomas Schoenborn for pointing me to this Optional
APAR.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

[phone]
"
IDMS 3rd-party providers forum
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Backward Migration from 16 to 15
"Hello All:



Last weekend I took two clients to IDMS Release 16.0 SP7 from 15.0 SP2 and
SP7.



Both Client sites have successfully backward migrated ADS/O dialogs with
changes and without changes.



I applied Optional APAR 251 to each IDMS 16.0 SP7 system and it worked like
a charm.



I am very grateful to Mr. Thomas Schoenborn for pointing me to this Optional
APAR.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

[phone]
"
IDMS Public Discussion Forum
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
DDLDCRUN - Expand Page
"Hi all,

I noticed that last month there was a brief discussion (""QUEUE RECORDS
WITH DMLO"") about how to do a DMLO on the DDLDCRUN area. (I had a look on
the listserv just now, after having no luck with the manuals & inside
DMLO.)

The issue that we have is that our DDLDCRUN area needs an Expand Page
done, as it is very full. And normally after we do an Expand Page on an
area, we test it inside DMLO just to check that all is OK.

I would prefer to stay away from the solution given in August to William
Allen's question, as we are real light on IDMS expertise here.

Please advise on the best way for me to test that my Expand Page on area
DDLDCRUN has worked successfully.

Thanks very much.
"
IDMS Public Discussion Forum
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
DDLDCRUN - Expand Page
"Hi all,

I noticed that last month there was a brief discussion (""QUEUE RECORDS
WITH DMLO"") about how to do a DMLO on the DDLDCRUN area. (I had a look on
the listserv just now, after having no luck with the manuals & inside
DMLO.)

The issue that we have is that our DDLDCRUN area needs an Expand Page
done, as it is very full. And normally after we do an Expand Page on an
area, we test it inside DMLO just to check that all is OK.

I would prefer to stay away from the solution given in August to William
Allen's question, as we are real light on IDMS expertise here.

Please advise on the best way for me to test that my Expand Page on area
DDLDCRUN has worked successfully.

Thanks very much.
"
IDMS 3rd-party providers forum
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Re: DDLDCRUN - Expand Page
"Hello Mike:

One quick test would be to run a print space before and after and look at
the record counts. Another quick way is to issue the QUED task online. Most
of the time you will find very old queue records and you can delete them
selectively with QUED PROMPT. When I do a QUED and see queue records for
DEBUGQUEUE, DME, KBOSS and USG that are over a year old I delete them all
using QUED PROMPT.

William M. Allen, Jr.
ARCH Consulting Associates, Ltd.
[phone]

[ca.portal.admin]

when migrating from 15 to 17 (might have also happened had me migrated
to
16) - we noted that all subsequent of cobol code ""OBTAIN .... USING""
now
requires a terminating period or semicolon (to enforce only one
character
string to be interpreted as the sort-key element name. we have
addressed
this as each program was compiled when a change is made.

we recently picked up a 3rd party productivity tool (i am really not
sure
which one) - and our developers want to compile EVERY program abd are
complaining about the number of precompiles failing due to this issue -
and want all such programs pre-identified

has anyone written a program/script to examine program source
repositories
looking for OBTAIN...USING .... DML? (and more importantly, willing to
share?)

thanks,
Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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.



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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] FW: [IDMS-L] finding all OBTAINING USING .....
"IS ro12490/1 to be the published fix corresponding to your test fix?

thanks,
Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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






From:
""Pereira, Carla E"" <[e-mail]>
To:
[e-mail]
Date:
09/01/2009 04:16 PM
Subject:
[IDMSVENDOR-L] FW: [IDMS-L] finding all OBTAINING USING .....
Sent by:
IDMS 3rd-party providers forum <[e-mail]>


Hi Chris - I don't have a utility to scan the source but I did write an
apar (TB99850) to help out with this situation. =20

The apar first changes the generic DML004 message issued in this case to
a more descriptive DML084. With the apar applied and optional bit
settings, you can control the severity of the DML084. This will allow
precompiles complete with a warning or successful return code. As you
have done, we strongly suggest that the programs are addressed and
corrected as encountered to add the terminator the OBTAIN USING DML.
However we have found situations like yours where it is helpful to not
have a hard error for this situation. Changing the severity to a
warning will allow the precompile step to complete but warn you that the
situation in the program needs to be addressed. Remember if FIND/OBTAIN
USING DML statement is not coded properly runtime errors can occur.

The apar can be requested by opening an issue with Technical Support.
It has not been officially published yet.

Thanks, Carla


Carla Pereira
CA=20
Sr Sustaining Engineer
Tel: [phone]
Fax: [phone]
[e-mail]

[ca.portal.admin]

when migrating from 15 to 17 (might have also happened had me migrated
to
16) - we noted that all subsequent of cobol code ""OBTAIN .... USING""
now
requires a terminating period or semicolon (to enforce only one
character
string to be interpreted as the sort-key element name. we have
addressed
this as each program was compiled when a change is made.

we recently picked up a 3rd party productivity tool (i am really not
sure
which one) - and our developers want to compile EVERY program abd are
complaining about the number of precompiles failing due to this issue -
and want all such programs pre-identified

has anyone written a program/script to examine program source
repositories
looking for OBTAIN...USING .... DML? (and more importantly, willing to
share?)

thanks,
Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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.



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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Re: FW: [IDMS-L] finding all OBTAINING USING .....
"also - when will this fix be unleashed upon the unsuspecting public?
(the PIB documenting this fix was released yesterday)

Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] FW: [IDMS-L] finding all OBTAINING USING .....
"also - when will this fix be unleashed upon the unsuspecting public?
(the PIB documenting this fix was released yesterday)

Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] FW: [IDMS-L] finding all OBTAINING USING .....
"Hi Chris - yes RO12491 will be the PTF number which corresponds to
TB99850 (which is for z/OS). RO12490 is the z/VSE version of the fix.
These PTFs are going through our internal publication process which
involves extensive testing by our QA group before being released
publicly. This process usually takes about two weeks provided there are
no issues found with the PTFs. I expect these PTFs will be available
later next week. The PIB you mentioned (RI12747) documents the new
error message introduced by the PTFs. Since it doesn't include a fix
that needs tested it was released immediately.

Thanks, Carla

Carla Pereira
CA
Sr. Sustaining Engineer
Tel: [phone]
Fax: [phone]
[e-mail]

[ca.portal.admin]

when migrating from 15 to 17 (might have also happened had me migrated
to
16) - we noted that all subsequent of cobol code ""OBTAIN .... USING""
now
requires a terminating period or semicolon (to enforce only one
character
string to be interpreted as the sort-key element name. we have
addressed
this as each program was compiled when a change is made.

we recently picked up a 3rd party productivity tool (i am really not
sure
which one) - and our developers want to compile EVERY program abd are
complaining about the number of precompiles failing due to this issue -
and want all such programs pre-identified

has anyone written a program/script to examine program source
repositories
looking for OBTAIN...USING .... DML? (and more importantly, willing to
share?)

thanks,
Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
[e-mail]

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.



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
[e-mail]
SMTP
[e-mail]
[e-mail]
SMTP








Normal

Normal
Re: FW: [IDMS-L] finding all OBTAINING USING .....
"Hi Chris - yes RO12491 will be the PTF number which corresponds to
TB99850 (which is for z/OS). RO12490 is the z/VSE version of the fix.
These PTFs are going through our internal publication process which
involves extensive testing by our QA group before being released
publicly. This process usually takes about two weeks provided there are
no issues found with the PTFs. I expect these PTFs will be available
later next week. The PIB you mentioned (RI12747) documents the new
error message introduced by the PTFs. Since it doesn't include a fix
that needs tested it was released immediately.

Thanks, Carla

Carla Pereira
CA
Sr. Sustaining Engineer
Tel: [phone]
Fax: [phone]
[e-mail]