ca.portal.admin

IDMS and Hitachi's True copy/mirroring or similar technology

Discussion created by ca.portal.admin on May 20, 2005
It has been a long time since I posted here, but I have been reading
most of inbound emails. First of all, sorry about the 'CHANGE EMAIL'
command that was posted earlier to the IDMS-L. It just figures that I
have not posted for years and my first post is a blunder. :-)

I do have a question that applies to Hitachi's mirroring technology, but
it also could relate to EMC and shark drive etc. users.

We are required to use Hitachi's True copy (disk) mirroring to send
updates to a disaster recovery site. Hitachi's documents specific
procedures for some database such as Oracle, but none for CA-IDMS that
we can find. I have asked CA Support (via online). They discussed it
with development and they could not come up with any know procedures.

Is anyone using True Copy and Mirroring with CA-IDMS? If yes, do you:

a. Duplicate file/area updates and send the journals, or
b. Just send the journals and roll forward etc? If you only send the
journals you could have issues with library updates... etc. so it makes
sense to send certain file updates.

If you send the journals, does anyone know of any utilities that will
apply them as they are received on a continuous basis etc. We could
automate it using current batch utilities, but I was wondering what
others were doing if you are using this type of live mirroring to get
disaster backups across the country. We must also be able to recover
fairly quickly in the event of a disaster.

Thank You in advance.

Michael Zechman
DISA Database Support/DECC Mechanicsburg
(717) 605-7281

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS and Hitachi's True copy/mirroring or similar technology
"Mike,

For most hardware mirroring solutions you need to mirror the databases and
journals so that CA-IDMS can restart successfully. This means that all
writes to the mirrored disks will be transferred to the backup site - don't
underestimate the amount of bandwidth required for this! Just mirroring the
journals is probably not going to be enough.

Disaster recovery using a mirroring solution assumes that all CA-IDMS
datasets (databases, logs, loadlib, applications) are all time-consistent
with each other - using this model, offsite restart is similar to what
would happen if you had a simple power outage or system crash at the
primary site. CA-IDMS restarts by examining the online disk journals and,
if necessary, it rolls out in-flight recovery units before it accepts new
work. The concept is restart - not recovery (i.e. restore and roll-forward)
per se.

Our company provides a software-based CA-IDMS shadowing solution called
E-NET2. It permits ongoing journal processing against a ""shadow"" database
and handles in-flight recovery units correctly and also permits parallel
roll-forward executions. In addition we provide a product called RRDF which
captures CA-IDMS journal data and feeds it to offsite recovery and/or
shadowing processes. These technologies offer alternatives to straight
hardware mirroring and in some cases are complementary to mirroring.

Feel free to contact me off-list if you want to know more. Also you could
visit our website at http://www.enet.com

Best regards.
Tom Flesher
E-Net Corporation




""ZECHMAN, MIKE
(Contractor)""
<ZechmanM.ctr@MEC To
H.DISA.MIL> IDMS-L@LISTSERV.IUASSN.COM
Sent by: IDMS cc
Public Discussion
Forum Subject
<IDMS-L@LISTSERV. IDMS and Hitachi's True
IUASSN.COM> copy/mirroring or similar
technology

05/20/2005 11:56
AM


Please respond to
IDMS Public
Discussion Forum
<IDMS-L@LISTSERV.
IUASSN.COM>






It has been a long time since I posted here, but I have been reading
most of inbound emails. First of all, sorry about the 'CHANGE EMAIL'
command that was posted earlier to the IDMS-L. It just figures that I
have not posted for years and my first post is a blunder. :-)

I do have a question that applies to Hitachi's mirroring technology, but
it also could relate to EMC and shark drive etc. users.

We are required to use Hitachi's True copy (disk) mirroring to send
updates to a disaster recovery site. Hitachi's documents specific
procedures for some database such as Oracle, but none for CA-IDMS that
we can find. I have asked CA Support (via online). They discussed it
with development and they could not come up with any know procedures.

Is anyone using True Copy and Mirroring with CA-IDMS? If yes, do you:

a. Duplicate file/area updates and send the journals, or
b. Just send the journals and roll forward etc? If you only send the
journals you could have issues with library updates... etc. so it makes
sense to send certain file updates.

If you send the journals, does anyone know of any utilities that will
apply them as they are received on a continuous basis etc. We could
automate it using current batch utilities, but I was wondering what
others were doing if you are using this type of live mirroring to get
disaster backups across the country. We must also be able to recover
fairly quickly in the event of a disaster.

Thank You in advance.

Michael Zechman
DISA Database Support/DECC Mechanicsburg
(717) 605-7281

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Sending a msessage to the console
"Hi all:

We have a product that reads messages from the z/os console. Because of
that, we want a send messages to that console from ads application. Is there
any way to do that ???
The idea is manage some special events automatically.

TIA.

Javier S.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

"
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] Sending a message to the console
"yes indeedy - do a display from the ads console, and modify your WTOEXIT
to handle the display
for example, when record xxxxx is stored or modified , a database
procedure is called:
.
.
.
WRTMSG #WTL MSGID='9999990', X
PLIST=SYSPLIST, X
RGSV=(R3-R7), X
MSGDICT=YES, X
PARMS=PARM1
.
.
.
then, this code (hopefully) submits a batch job similarly to the process
for a jhournal or log offload when DC message
999999 is written


***********************************************************************
******** HUMANA INC CHANGE #5 BEGIN - CHK FOR DC999999 ********
***********************************************************************
LA R15,AUTHSUB
CLC WTOMTEXT(13),=C'IDMS DC999999' IF SPECIAL MESSAGE
BE SAVEREGS
***********************************************************************
******** HUMANA INC CHANGE #5 END - CHK FOR DC999999 ********
***********************************************************************
.
.
.
***********************************************************************
******** HUMANA INC CHANGE #6 BEGIN - US SUBMIT ********
***********************************************************************
AUTHSUB LA R6,WTOMTEXT LOAD MSG ADDR TO R6
LH R5,WTOMLEN LOAD MSG LEN TO R5
AR R6,R5 ADD LEN REG TO ADDR REG
LA R5,WTOMTEXT+10 LOAD MSG ADDR (+10) TO R5
NEXCHAR3 LA R5,1(R5) INCREMENT CURRENT MSG CHAR (R5)
CR R5,R6 COMPARE CURRENT POS TO END
BH RETURN IF WE ARE PAST END, GET OUT
CLI 0(R5),C'*' CHECK IF THIS CHAR IS AN *
BNE NEXCHAR3 IF NOT, CHECK NEXT CHAR
RUNAUTH LA R0,0
L R15,=A(SETAMODE)
BALR R14,R15
OPEN (JESRDR,(OUTPUT)) OPEN THE IN AND OUT DATASETS
OPEN (AUTHJOB,(INPUT))
NEXTONE2 GET AUTHJOB,CARD GET THE FIRST/NEXT INPUT REC
LA R8,CARD LOAD CARD ADDR INTO R8
LH R7,=H'50' LOAD CARD LEN INTO R7
AR R8,R7 ADD LEN REG TO ADDR REG
LA R7,CARD LOAD CARD ADDR INTO R7
NEXCHAR4 LA R7,1(R7) LOOK AT NEXT CHAR IN CARD
CR R7,R8 ARE WE AT END?
BH PUTJES2 IF SO, WRITE IT!
CLI 0(R7),C'?' LOOK FOR A QUESTION MARK
BNE NEXCHAR4 IF NOT, CHECK NEXT CHAR
CLC 0(11,R7),=C'???????????' LOOK FOR ???????????
BNE PUTJES2 IF NOT, WRITE IT!
MVC 0(20,R7),1(R5) COPY THE NEXT 20 MSG CHAR TO CARD
MVC 21(1,R7),=X'7D' ADD A CLOSING QUOTE
PUTJES2 PUT JESRDR,CARD WRITE THE JCL CARD
B NEXTONE2 GET THE NEXT JCL CARD
CLOSE4 CLOSE (JESRDR)
CLOSE (AUTHJOB)
LA R0,1
L R15,=A(SETAMODE)
BALR R14,R15
***********************************************************************
******** HUMANA INC CHANGE #6 END - US SUBMIT ********
***********************************************************************






Chris Hoelscher
IDMS & DB2 Database Administrator
Humana Inc
502-580-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
Re: Sending a msessage to the console
"Javier,

I am going to assume that you just want the message to go to the MVS
console, where you will have some method of detecting it and taking some
action. In that case...

I'm not an ADS guy, but I do this for some messages. If your message is
defined in the dictionary, I believe all you need to do is change the
destination of the message to OPERATOR. I did this for some standard CA
messages since I wanted them to go to the console so I could ""grab"" them in
WTOEXIT.

Example:

MOD
MESSAGE NAME IS DC274001
INCLUDE TEXT LINE IS 1
DESTINATION IS OPERATOR.

Maybe you can specify a destination in your ADS code if you don't get the
message from the dictionary?

Joe Lupico
IDMS System Support
""Our World is a Happy World""

Outcomes