HP3000-L Archives

August 2007, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Walter J. Murray" <[log in to unmask]>
Reply To:
Walter J. Murray
Date:
Wed, 15 Aug 2007 20:43:45 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
We had a system interruption at one of our remote sites yesterday, and
someone at the site brought the system back up without telling us.
Consequently, we didn't go through the usual procedures.

Fortunately, there hasn't been any serious fallout, except that a batch
job  aborted last night because of a CM KSAM file that needed to be
recovered (FSERR 192, SYSTEM FAILURE OCCURRED WHILE THE KSAM FILE WAS
OPENED).

It got me to thinking, and I have some questions for the group.

1.  Is KSAM XL reasonably robust in the event of a system interruption?
Would this be a good reason to convert the file from CM KSAM to KSAM XL?

2.  If we converted all our CM KSAM files to KSAM XL, are there any
problems we would be likely to encounter?  I can't think of any program
changes we would need to make.  Am I being overly optimistic?  We are
primarily a COBOL and PowerHouse shop.

Thanks for sharing your experiences.  

Walter  

Walter J. Murray

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2