ca.portal.admin

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

Discussion created by ca.portal.admin on Sep 1, 2009
Latest reply on Sep 1, 2009 by 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
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
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: +1-508-628-8207
Fax: +1-508-820-4361
Carla.Pereira@ca.com

Outcomes