Walter,
We are also a Cobol/PowerHouse shop and a couple of years ago we
converted to KSAM/XL. We have had no problems with them at all. The only
changes required were to some batch jobs where we replaced the KSAMUTIL
BUILD commands with ':BUILD ...;KSAMXL' and removed the 'KSAMUTIL
KEYINFO;RECOVER' commands.
Extract from 'Using KSAM XL and KSAM 64' reference manual:
Recovering from a System or Software Abort
File recovery after a system or software abort is provided automatically
through transaction management. After a file has been created with the
BUILD command or has been created and loaded using the HPFOPEN or FOPEN
intrinsics, it is attached to system logging. If processing of a
transaction is interrupted prior to its logical completion, the
transaction is rolled back before processing is allowed to continue. A
transaction is rolled back in the following cases:
*A system abort occurs.
*A process with an active logical transaction aborts.
*A transaction aborts.
*A transaction causes a deadlock condition.
If a KSAM file is created and loaded using FCOPY's NEW option, or an
HPFOPEN or FOPEN intrinsic call, transaction logging is not attached
until the file is closed. This provides a fast load mode that loads the
file more quickly than if transaction logging was invoked. An abort
during this load process, however, is not logged. If an abort occurs
when creating and loading a file with FCOPY's NEW option or with the
HPFOPEN or FOPEN intrinsic, restart the file loading process.
To protect initial loading, use the BUILD command to create the file.
The file is attached to transaction management when the BUILD command is
used. A file can also be attached manually by creating and loading the
file with the HPFOPEN intrinsic and specifying the DOMAIN=CREATE option.
With this option, the file is attached and system logging begins with
the first access.
regards,
Robert W.Mills
Business Systems Development Analyst
Group Information Systems & Technology
Pinnacle Arvato
DDI: +44 (0)20 8309 3604
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Walter J. Murray
Sent: 16 August 2007 04:44
To: [log in to unmask]
Subject: [HP3000-L] CM KSAM vs. KSAM XL, recovering after system
interruption
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 *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
