ca.portal.admin

Re: Fw: unsubscribe

Discussion created by ca.portal.admin on Nov 14, 2007
We get folks dropping from the list all the time and joining as well.
Normally you don't get the message as they send a message to the listserv
(listserv@listserv.iuassn.com) with signoff idms-l or signoff * in the
body. These commands will remove the person from idms-l or if the * is
used, then idms-l and idms-vendor-l.

Bob Wiklund
Tiburon Technologies
623 594-6022

________________________________

From: IDMS 3rd-party providers forum on behalf of Chris Hoelscher
Sent: Wed 11/14/2007 9:58 AM
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM
Subject: Re: Fw: unsubscribe



man - what is up - they are droppin like flies ..... was it something i
said?

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.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Fw: unsubscribe
"We get folks dropping from the list all the time and joining as well. Normally you don't get the message as they send a message to the listserv (listserv@listserv.iuassn.com) with signoff idms-l or signoff * in the body. These commands will remove the person from idms-l or if the * is used, then idms-l and idms-vendor-l.

Bob Wiklund
Tiburon Technologies
623 594-6022

________________________________

From: IDMS 3rd-party providers forum on behalf of Chris Hoelscher
Sent: Wed 11/14/2007 9:58 AM
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM
Subject: Re: Fw: unsubscribe



man - what is up - they are droppin like flies ..... was it something i
said?

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.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Fw: unsubscribe
"man - what is up - they are droppin like flies ..... was it something i
said?

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: R16 Two phase Commit
"I believe you must make preparations for this error message (it has never occurred here, but reading about it gives me shivers):
DC329024 V73 REPLY 01 T23 REPLY WITH RESYNCHRONIZAT
We are using Console Operator Automation to reply and alert us -- your requirements may differ.

QO70635 is essential, and a little tricky to put on (not standard SMP/E). I failed to get all the modules applied successfully in the third of our production environments, so RRS would not work correctly (at all), and getting it fixed was a real hair-puller for us and 2nd level support.

NEED ENABLE_RRS=ON IN SYSIDMS of a batch job

RRS CALL MODULES ARE MQ****, INSTEAD (but NOT EXACT corollaries to other MQ module prefixes).

RRS LINKEDIT STUB IS CSQBRRSI, INSTEAD

IDMS COMMIT UNDER RRS IS REALLY A ""PREPARE"", SORT OF ... nothing is committed until you do the MQCMIT.

You MUST issue a FINISH for a successfully commited 2-phase run-unit, but it is NOT necessary to issue a ROLLBACK for a failed one -- the MQRBAK will take care of it.

There are 2 or 3 common error codes you will get back from MQ / RRS -- I don't remember the Code-IDs, since we have gotten over the learning-curve-hump so long ago, but basically they were:
- MQ Queue full
- RRS not ready (initialized)
- Parameter list wrong for MQ call.

Of all the things for which it is important to have a POC / demo program, this would be among the most important.

Regards,
dem

Outcomes