ca.portal.admin

Turning Sharing On

Discussion created by ca.portal.admin on Dec 1, 2010
We are in the process of upgrading to IDMS-17. In our first attempt to we discovered a deadlock issue that CA deemed as a hole in the software that was fixed in IDMS-16 SP7 (we did not apply SP7). CA's explanation: It appears that as Release 17 was being developed, a condition in the code was found which was incorrectly causing transactions being executed on the same terminal to share a transaction structure when transaction sharing was not enabled. We were instructed to turn SHARING ON (we have always had this turned off) to correct our deadlock issues. We are now experiencing currency issues and 1419 error codes when calling out to a DC program - (which use a FINISH before returning). Has anyone run into this issue and if so - do you have any advice?


Thanks,
Systems Analyst
Elaine Bugger
Olin Brass/Global Brass and Copper
Elaine.Bugger@olinbrass.com





The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this message and any attachments in error and that any review, dissemination, distribution, copying or alteration of this message and/or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by electronic mail, and delete the original message.

This E-Mail has been scanned for viruses.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Convert IDMS from NONSMS to SMS
"How can I convince management and other IS support personnel about
converting from non sms environment to a SMS environment.

Is there a good business savings presentation for doing this conversion?
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Convert IDMS from NONSMS to SMS
"How can I convince management and other IS support personnel about
converting from non sms environment to a SMS environment.

Is there a good business savings presentation for doing this conversion?
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Convert IDMS from NONSMS to SMS

 
Steve,  from my experience,  SMS does nothing for IDMS database administration. 
When SMS was  implemented in my shop,  we excluded the IDMS DASD from SMS.
 
SMS might be a benefit for DB2 but that is a subject for another listserv.  :-)
 
 
--- On Wed, 12/1/10, Steve Carlson <steve.carlson@NSC.COM> wrote:


From: Steve Carlson <steve.carlson@NSC.COM>
Subject: Convert IDMS from NONSMS to SMS
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM
Date: Wednesday, December 1, 2010, 5:30 PM


How can I convince management and other IS support personnel about
converting from non sms environment to a SMS environment.

Is there a good business savings  presentation for doing this conversion?
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Convert IDMS from NONSMS to SMS
"It has been beneficial to us.
We have moved to mod9s and mod27s from mod3s.
PAV is a must-have.

We no longer worry, therefore, about dataset placement, nor really about file-size, as we used to. We just let SMS place the datasets... including Journal files, which used to be on dedicated volumes.

We do still limit file-size such that it is easier to ""Tetris"" all the files into our available space, but we no longer arbitrarily limit the %utilization of a disk drive. So that is a tangible economic benefit, too.

We used to have to do a lot of ""tuning"" to correct DASD & Channel performance bottlenecks as the application evolved, but now we do not. This benefits DBA (& the company of course) by removing the need for the outages to move datasets around and the drudgery (& risk) of manual load balancing.

A good, experienced Storage Manager (person) helps the transition a great deal -- although it seems like a straight-forward process writing SMS rules, everyone seems to stumble over it the first few attempts ... the learning curve is painful for all concerned.

A little DBA training in SMS STORCLAS, MGMTCLAS, & DATACLAS overrides -- and the ACF2/RACF authority to use them -- makes overcoming shortcomings in the SMS rules possible, and easy.

Regards,
dem

Outcomes