I agree with Tony and Robert, but I would add
:SETDUMP
to arm the debug facility first, that may give more information.
-Craig
Tony Summers <[log in to unmask]> wrote:
The method mentioned by the other poster can also be extended.
If you re-direct the $STDLIST to a spoolfile (and you have the relevant
software) then you tail the spoolfile - thus proving exactly where the
problem is in the program.
On one session :
File lp;dev=lp,2
Rnu program >*Lp
Then on a second session you can tail the spoolfile (ie. Observe the
contents of the spoolfile as it is being written to). We're using
netbase spool to tail them !
We use this method during testing to add displays to a program when we
have a problem inside a view based program. However, remember to
remove the displays before putting into production !
The other thought that comes to mind is to add some preliminary checks
in your program before entering view - for example opening your KSAM
files for input and re-closing them. This might reveal some differences
in the environment that you haven't thought about.
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Kishan P
Sent: 15 March 2007 13:20
To: [log in to unmask]
Subject: [HP3000-L] Help for the screen failure problem in run-time.
Hello All,
Could you please help us in resolving this problem?
Please have a look at the below description.
We use VFORM screens. Whenever any screen changes are done, those
attribute changes will be stored in 3 KSAM files.
We've changed one screen (Removing ADD mode), and subsequently one
background job updates the KSAM files.
Now, we do all the changes in our DEVELOPMENT account and then those
modules are moved to TRIAL account for User Acceptance Testing.
And later on that module will be moved to PRODUCTION account finally.
The same screen works perfectly in DEVELOPMENT & TRIAL accounts, without
any error. But it fails in PRODUCTION account.
It's just giving an error message in run time "Program terminated in an
error state (CIERR 976) "
We are unable to debug the root cause for this failure.
Could you please help us in this problem?
Thanks & Regards,
Jai Kishan P.
=====-----=====-----=====
Notice: The information contained in this e-mail message and/or
attachments to it may contain confidential or privileged information. If
you are not the intended recipient, any dissemination, use, review,
distribution, printing or copying of the information contained in this
e-mail message and/or attachments to it are strictly prohibited. If you
have received this communication in error, please notify us by reply
e-mail or telephone and immediately and permanently delete the message
and any attachments. Thank you
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
The contents of this email are confidential to the intended recipient and may not be disclosed. Although it is believed that this email and any attachments are virus free, it is the responsibility of the recipient to confirm this.
Details of Smith & Williamson group companies and Nexia Smith & Williamson Audit Limited and their regulators (where applicable), can be found at this URL
http://www.smith.williamson.co.uk/disclosure
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
---------------------------------
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
