ca.portal.admin

migration from PMDC to Performance Monitor

Discussion created by ca.portal.admin on Jul 6, 2009
Latest reply on Jul 8, 2009 by ca.portal.admin
Hi,



we are thinking about a migration from the PMDC to the
Performance Monitor from CA. Is there somebody who has
experiences with such a migration?

In the moment we're using the PMDC to write SMF-record but also
as a monitor to control the CVs with several settings e.g. to
abend tasks when they are using too much storage, CPU, ...



Best regards



Josef Lust



T-Systems Enterprise Services GmbH

Computing Services & Solutions (CSS)

Application Line Automotive & Manufacturing

Josef Lust

IDMS/MQS & SAG Services

Emmy-Noether-Str. 17, D-76131 Karlsruhe

+49 721 8932- 424 (Phone)
+49 1805 33 44 91 - 05 94 (Fax)
+49 173 950 1358 (Mobile)
E-Mail: Josef.Lust@t-systems.com <mailTo:Josef.Lust@t-systems.com>
Internet: http://www.t-systems.com <http://www.t-systems.com/>
Mailbox of function group: HOTLINE.ALAM.IDMS-MQS@t-systems.com



T-Systems Enterprise Services
<https://systemsnet.telekom.de/tool/de_systemswiki/index.php/Ent
erprise_Services> GmbH

Supervisory Board: René Obermann (Chairman)

Board of Management
<https://systemsnet.telekom.de/tool/de_systemswiki/index.php/Man
agement> : Reinhard Clemens (Chairman), Olaf Heyden, Joachim
Langmack, Dr. Matthias Schuster, Klaus Werner

Commercial register: Amtsgericht Frankfurt am Main HRB 55933

Registered office: Frankfurt am Main

WEEE -Reg.-No. DE87523644



Notice: This transmittal and/or attachments may be privileged
or confidential. If you are not the intended recipient, you are
hereby notified that you have received this transmittal in
error; any review, dissemination, or copying is strictly
prohibited. If you received this transmittal in error, please
notify us immediately by reply and immediately delete this
message and all its attachments. Thank you.



T-Systems - Business flexibility
<https://systemsnet.telekom.de/tool/de_systemswiki/index.php/Bus
iness_flexibility>


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
Re: migration from PMDC to Performance Monitor
"as far as i can tell - the CA-Performance Monitor add-on for IDMS does NOT
allow for auto-cancelling when a predetermined criteria is met
if the SMF reporting and auto-cancel features are important to you and
PMDC performs those functions - you might be better off to stay with PMDC



at our site - we use CA=PerfMon for the SMF reporting, and ASG-Prealert
for auto-cancelling feature (in fact - when any predetermined criteria is
met, not only can you cancel the offending task - ASG-Prealert will
optionally submit a batch job with criteria-dependent tokens of your
choosing, so that you can send emails with pertinent information - or do
whatever your site deems appropriate

in this example - ASG-PreAlert pulls in this JCL when an ""event"" is
detected - replaces &CVNO with cv# and &MSGA with the PreAlert-generated
message - and we pass the output to a program that uses that info in an
email


//ICEMAN EXEC PGM=ICEMAN
//* ** ICEMAN SORT **
//ALTPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=D
//SYSOUT DD SYSOUT=*
//SORTIN DD *
CV&CVNO &MSGA
//SORTOUT DD DSN=&&WORK01,
// DISP=(,PASS),
// UNIT=VIO
//SORTWK01 DD SPACE=(CYL,(50)),
// UNIT=SYSDA
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
SORT FIELDS=COPY
END






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] migration from PMDC to Performance Monitor
"as far as i can tell - the CA-Performance Monitor add-on for IDMS does NOT
allow for auto-cancelling when a predetermined criteria is met
if the SMF reporting and auto-cancel features are important to you and
PMDC performs those functions - you might be better off to stay with PMDC



at our site - we use CA=PerfMon for the SMF reporting, and ASG-Prealert
for auto-cancelling feature (in fact - when any predetermined criteria is
met, not only can you cancel the offending task - ASG-Prealert will
optionally submit a batch job with criteria-dependent tokens of your
choosing, so that you can send emails with pertinent information - or do
whatever your site deems appropriate

in this example - ASG-PreAlert pulls in this JCL when an ""event"" is
detected - replaces &CVNO with cv# and &MSGA with the PreAlert-generated
message - and we pass the output to a program that uses that info in an
email


//ICEMAN EXEC PGM=ICEMAN
//* ** ICEMAN SORT **
//ALTPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=D
//SYSOUT DD SYSOUT=*
//SORTIN DD *
CV&CVNO &MSGA
//SORTOUT DD DSN=&&WORK01,
// DISP=(,PASS),
// UNIT=VIO
//SORTWK01 DD SPACE=(CYL,(50)),
// UNIT=SYSDA
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
SORT FIELDS=COPY
END






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
Restructure a field used as a key in an index
"Hello All:



I have not done this in a very long time so I thought I would ask for some
advice from the list members.



I need to restructure an element from PIC X to PIX X(3), the issue is that
this element is used as an index key in a system owned index and the index
structure (SR7 & SR8) resides in the same physical area as the data that is
indexed (not my design).



The restructure is simple, my question is do I just to an index rebuild
after the restructure or do I need to delete the index before the
restructure and then build it after the restructure?



Any help or comments would be appreciated.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Restructure a field used as a key in an index
"Hello All:



I have not done this in a very long time so I thought I would ask for some
advice from the list members.



I need to restructure an element from PIC X to PIX X(3), the issue is that
this element is used as an index key in a system owned index and the index
structure (SR7 & SR8) resides in the same physical area as the data that is
indexed (not my design).



The restructure is simple, my question is do I just to an index rebuild
after the restructure or do I need to delete the index before the
restructure and then build it after the restructure?



Any help or comments would be appreciated.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Restructure a field used as a key in an index
"I believe a rebuild is enough (from members or from all-rows, if it is
mandatory).
Take a look at the Data Administration Guide vol 2. Chapter 32 - Modifying
Schema Entities (Release 16), there may be additional useful information.
Chapter 32.6 addresses index modifications.

If you are changing the control length of the record you should use
IDMSRSTC to create the macro. If you are unsure whether you are changing
the control length, use the IDMSRSTC program as well.

If this is a heavily used index and area, you should consider splitting it
so the data is in one part of the area and the index in another, by using
offsets. It would require an unload/reload. It is by no way perfect, but
more practical than creating a new area for the index, which would require
program changes.

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

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




""William M.
Allen, Jr.""
<archcons@BELLSOU To
TH.NET> IDMS-L@LISTSERV.IUASSN.COM
Sent by: IDMS cc
Public Discussion
Forum Subject
<IDMS-L@LISTSERV. Restructure a field used as a key
IUASSN.COM> in an index


07/06/2009 10:00
AM


Please respond to
archcons@bellsout
h.net






Hello All:



I have not done this in a very long time so I thought I would ask for some
advice from the list members.



I need to restructure an element from PIC X to PIX X(3), the issue is that
this element is used as an index key in a system owned index and the index
structure (SR7 & SR8) resides in the same physical area as the data that is
indexed (not my design).



The restructure is simple, my question is do I just to an index rebuild
after the restructure or do I need to delete the index before the
restructure and then build it after the restructure?



Any help or comments would be appreciated.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
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: Restructure a field used as a key in an index
"I believe a rebuild is enough (from members or from all-rows, if it is
mandatory).
Take a look at the Data Administration Guide vol 2. Chapter 32 - Modifying
Schema Entities (Release 16), there may be additional useful information.
Chapter 32.6 addresses index modifications.

If you are changing the control length of the record you should use
IDMSRSTC to create the macro. If you are unsure whether you are changing
the control length, use the IDMSRSTC program as well.

If this is a heavily used index and area, you should consider splitting it
so the data is in one part of the area and the index in another, by using
offsets. It would require an unload/reload. It is by no way perfect, but
more practical than creating a new area for the index, which would require
program changes.

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

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




""William M.
Allen, Jr.""
<archcons@BELLSOU To
TH.NET> IDMS-L@LISTSERV.IUASSN.COM
Sent by: IDMS cc
Public Discussion
Forum Subject
<IDMS-L@LISTSERV. Restructure a field used as a key
IUASSN.COM> in an index


07/06/2009 10:00
AM


Please respond to
archcons@bellsout
h.net






Hello All:



I have not done this in a very long time so I thought I would ask for some
advice from the list members.



I need to restructure an element from PIC X to PIX X(3), the issue is that
this element is used as an index key in a system owned index and the index
structure (SR7 & SR8) resides in the same physical area as the data that is
indexed (not my design).



The restructure is simple, my question is do I just to an index rebuild
after the restructure or do I need to delete the index before the
restructure and then build it after the restructure?



Any help or comments would be appreciated.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: z/OS R1.10 upgrade
"We are in the process of making an even bigger leap. We are currently
running on Rel 14.1 sp3 for IDMS and our OS is os/390 v2r10. We have
started the conversion to z/OS 1.10. Brought up our test cv yesterday
on the 1.10 with no changes, except adding ALLOWUSERKEYCSA(yes) to the
system parms. Everything seems to be running smoothly. We hope to
complete this conversion by the end of August.


Thanks,
Randy Bunton
Database Administrator
Charleston Water System

Outcomes