ca.portal.admin

COMMIT question

Discussion created by ca.portal.admin on Mar 3, 2009
Latest reply on Mar 5, 2009 by ca.portal.admin
What types of commit (if any) will cause acquired storage to be
released?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
idms 17 opportunity # 3
"a user at our site reported that an olq-menu generated report appeared
scrambled on her MOD2 terminal (MOD4s appear to display the report
correctly) - should you experience this - know that it IS a known issue -
contact CA for details

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




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
idms 17 opportunity # 3
"a user at our site reported that an olq-menu generated report appeared
scrambled on her MOD2 terminal (MOD4s appear to display the report
correctly) - should you experience this - know that it IS a known issue -
contact CA for details

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




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
idms 17 (possibly 16 - we never went there) opportunity #4
"journal archives - when there are no bfor/aftr records to offload

in 15 - the journal offload would end with RC=4, would produce message
DB002529 C1M357: File JxJRNL - current segment empty

(and of course you would look at the report and see that the LORBN and the
HIRBN of the selected segment were the same)

most importantly (to us) - when there was nothing to offload, NO dataset
(tape in our case) mount was requested nor dataset cataloged

in 17 - when no bfor/aftr fo offload
still RC=4, the same message id# (DB002529) but a different accuimpanying
text:

no data was offloaded from selected journal(s)

but - something WAS offloaded -

DISK BLOCKS OFFLOADED 1 (but not sure where it was offloaded to - TAPE
BLOCKS WRITTEN THIS SEGMENT 0 and TOTAL TAPE BLOCKS WRITTEN 0

and ... (what has drawn our attention) - a offload dataset mount IS
requested and the dataset IS cataloged

so what?

in our of our divisions, our journal jobs have subseqent steps (creating a
D/R journal offload copy) - in the past - an RC=4 meant no tape was
created - the job can stop here - no problem
but now ... since a tape is created - and we want to keep the D/R GDG seq
# in sync with the inhouse copy - we now must continue to process on an
RC=4 because the tape was created - or do we - what else could an RC-4
mean???

we are consulting with CA to determine if this change was incidental or
intentional -- if the latter - then I guess we will just need to learn to
adapt .....

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




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
idms 17 (possibly 16 - we never went there) opportunity #4
"journal archives - when there are no bfor/aftr records to offload

in 15 - the journal offload would end with RC=4, would produce message
DB002529 C1M357: File JxJRNL - current segment empty

(and of course you would look at the report and see that the LORBN and the
HIRBN of the selected segment were the same)

most importantly (to us) - when there was nothing to offload, NO dataset
(tape in our case) mount was requested nor dataset cataloged

in 17 - when no bfor/aftr fo offload
still RC=4, the same message id# (DB002529) but a different accuimpanying
text:

no data was offloaded from selected journal(s)

but - something WAS offloaded -

DISK BLOCKS OFFLOADED 1 (but not sure where it was offloaded to - TAPE
BLOCKS WRITTEN THIS SEGMENT 0 and TOTAL TAPE BLOCKS WRITTEN 0

and ... (what has drawn our attention) - a offload dataset mount IS
requested and the dataset IS cataloged

so what?

in our of our divisions, our journal jobs have subseqent steps (creating a
D/R journal offload copy) - in the past - an RC=4 meant no tape was
created - the job can stop here - no problem
but now ... since a tape is created - and we want to keep the D/R GDG seq
# in sync with the inhouse copy - we now must continue to process on an
RC=4 because the tape was created - or do we - what else could an RC-4
mean???

we are consulting with CA to determine if this change was incidental or
intentional -- if the latter - then I guess we will just need to learn to
adapt .....

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




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
opportunity #4 continued
"one might ask ""how do you get a journal offload with NO bfor/aftr s to
offload?""

our site forces a journal offload after each normal CV shutdown ..... (so
its not triggered by the WTOEXIT)


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




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
opportunity #4 continued
"one might ask ""how do you get a journal offload with NO bfor/aftr s to
offload?""

our site forces a journal offload after each normal CV shutdown ..... (so
its not triggered by the WTOEXIT)


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




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: COMMIT question
"Storage type DB is impacted by COMMIT statements. USER KEPT and SHARED
KEPT are, as the name implies, KEPT until an explicit FREE STORAGE, or
in the case of USER KEPT, until the user signs off.

SHORT TERM and LONG TERM used to have to do with where in the storage
pool the storage was allocated (SHORT term at one end and LONG term at
another end to prevent conflict) - I'm not sure that this is still the
case.

Kay - if you could tell us what your issue is that might be useful.
Scratch and Queue elements are also storage based and are impacted by
COMMIT statements - so if you can explain the problem more fully you
might get more help?

HTH - cheers - Gary

Gary Cherlet
Justice Technology Services
Department of Justice, SA Government

"""""""" =20
@@ On this page I appear to be deeply concerned about one thing or
another .......=20
> this is merely an old habit of the face=20
/\ Leonard Cohen

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.

Outcomes