HP3000-L Archives

January 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:
Denys Beauchemin <[log in to unmask]>
Reply To:
Date:
Sat, 20 Jan 2007 19:57:14 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (155 lines)
Is this a new error?  Is this a new program?  Is there a reason why you are
using DBXBEGIN/DBXEND?

Denys

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Blanchard L. Carter
Sent: Saturday, January 20, 2007 6:22 PM
To: [log in to unmask]
Subject: [HP3000-L] Large transactions for XM

Does anyone know of a way to allow large transactions on the MPE HP3000
system?  I am getting an error message because the transactions I am trying
to put to the Turbo Image database must exceed the 4MB limit of the
transaction manager (XM article below).


The article mentions using the DBXBegin/DBXEnd.  I would appreciate any help
from the HP experts out there.

----------------------------------------------------------------------------
----------
(http://docs.hp.com/en/30216-90291/ch05s01.html)
Large Transactions for IMAGE Users   
 
By B T Vikram Kumar, B S Jyoti, Shobha Pradeep 
Commercial Systems Division
 
Background 
 
Of late many of the users of TurboIMAGE and IMAGE/SQL have the requirement
of transaction sizes larger than is currently possible today (4 MB). This is
true, especially for users who run applications involving bulk puts/ deletes
/updates. The situation becomes more difficult with the limitation of the
size of the Transaction Manager (XM) userlog, if the transactions are on the
same volume set. This integrated solution involving TurboIMAGE/iX, XM,
IMAGE/SQL and ALLBASE/SQL addresses these problems. The following sections
discuss these issues, and various options available to the users to overcome
these issues, as a result of this solution.
 
Current Limitations 
 
Version C.03.00 of TurboImage introduced the concept of dynamic transaction,
meaning the application can rollback a transaction at runtime. Later when
the Transaction Manager started handling the dynamic transactions, some
customers used to see the stalled transaction message due to the limit on
the size of the transaction.
----------------------------------------------------------------------------
----------
-------------- Original message -------------- 
From: [log in to unmask] 

Has anyone ever had this happen during a Cobol run on the HP3000 MPE system.
I am not sure what this error pertains to.  If anyone can help me I would
greatly appreciate it.  I am not sure if this is a I/O based error or a MPE
O/S based error.  It looks like a File system based error.  

At the time the program was doing a data load to the Turbo Image dataset in
our database.  Yet Suprtool reads the dataset fine/.

 :RUN BCHPROVX.emblc.AIHTEST
 BCHPROVS - Beechstreet Provider load program
                                    v 1.0
 Trans date: 20070119
 TIN is all zeroes or spaces, using SSN
.
.
. 
 **** STALLED TRANSACTION: EXCEEDED ACCUMULATED LOG DATA THRESHOLD
Ð
 WARNING ** One or more entries on the error stack have been overwritten.
Ð
 HPE Error Management message 205
Ð
ÐWARNING ** Message set 185, Error number 1030 was not found in the system
catalog.
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
ÐSpecifying the LONG MAPPED OPTION (item# 21) for this file type is invalid.
 (FILE OPEN ERROR -299)
Ð
 File System message 299
Ð
ÐSpecifying the LONG MAPPED OPTION (item# 21) for this file type is invalid.
 (FILE OPEN ERROR -299)
Ð
 File System message 299
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
 Intrinsic layer; an access violation occurred.
Ð
 File System message 3
Ð
ÐIntrinsic layer; the operation could not be completed because a nonexistent
 file was specified.
Ð
 File System message 38
Ð
 FLABELINFO intrinsic.
Ð
 SUBSYS_INTRIN_ID message 25
 ABORT: BCHPROVX.EMBLC.AIHTEST
 NM SYS   a.010 061ec dbg_abort_trace+$28
 NM USER  11e.00e9a378 PROC'EXIT000442+$78
 NM PROG  151.0002a084 bchprovs$001$+$4238

 Program terminated in an error state. (CIERR 976)
 REMAINDER OF JOB FLUSHED.
 CPU sec. = 2924.  elapsed min. = 70.  FRI, JAN 19, 2007,  4:02 PM.

* 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 *

ATOM RSS1 RSS2