15 replies to this topic

[Matthews Estrice]

Hi everyone,

For some reason, when I press slash enter on the enquiry screen I end up in
error link,but if I use F3 (EOD) I.E OK.

I am intending to link the error page on the error link in the function.
This error page would display COMMS VARIABLE almost the same as @SYSLOOK.

Regards,
Matthews

[Joseph Bove]

Matthew,

As far as I know, ProIV has always worked that way.

What error are you specifically trying to trap for in order to send them to your alternate screen?

Regards,

Joseph

[Lewis Mccabe]

Error link is from years ago before exit and EOD logic points existed. Yes, when you cancel the system runs the error link function. We very, very, rarely use an error link. If you need to conditionally link, do it in exit or EOD logic. FNKEY 9 is cancel and 10 is EOD.

Lew

[Matthews Estrice]

Hi Joseph,

First of all I want to send the error parameters to an XML page then send the parameters
to the JAVA mail API (bugtrack website) and the MMS/SMS.The user do not give all information and
the users just reboot the systems. I am looking at some error exception handling without having to
using the error logic,but looking at the overral function.I would like to know who the user,company,@TFUNCT
@LFUNCT,@#COMMS,@$COMMS, @DATE, @TIME
I am basically trying to trap errors like :-


@RFUNCT
11:10:45 COMMUNICATIONS MENU NAM/SYS/TTYP24
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
The following error occurred, causing your function to COM.HOTR
be aborted and an automatic rollback to be performed. 11:10:49

@MSG [ 18]
@MSGTEXT [018 - ERROR IN WRITING FILE - ]
@MSGARGS [COM-HOTR ]

@SYSERR [0 ]
@SYSERRTEXT [ ]

Press [ ]

[Joseph Bove]

Matthew,

Paul's basically got it.

The error link is for a user canceling out of the screen. It's coded as @EFUNCT or set in the function via the error link tag.

The error screen is @RFUNCT.

It would probably clarify things more in future releases of ProIV to refer to the exit link at the EOD link and the error link as the Cancel link... or simply drop the error link altogether.

@EFUNCT is meaningless in anything other than screen or menu functions (as far as I know).

Regards,

Joseph

[Matthews Estrice]

Thank you to everyone who contributed.
This works like a bomb.
I am happy.

Regards,
Matthews

[Richard Bassett]

@EFUNCT is meaningless in anything other than screen or menu functions (as far as I know).

I think that is indeed true.
FWIW, for "server side" reports/updates I have often defined/used @EFUNCT to be the link function for "application initiated aborts" - ie. whenever the application detects some exception/situation it can't deal with silently then log some diagnostics, set @LFUNCT=@EFUNCT and FNEXIT. Obviously you can encapsulate this in global logic.

[Chris Pepper]

The "Error link" from Reports or Updates gets called in situations such as the Primary file on LU1 being invalid.

I just ran a test on this in 4.6 to check what I'd been teaching for the last 15 years was still vaguely true!

BTW "works like a bomb" describes a lot of my code... e.g. explodes without warning devastating the local area!

[Bob Filipiak]

BTW "works like a bomb" describes a lot of my code... e.g. explodes without warning devastating the local area! 

Chris,

YOU Too!!!!!

I have that same problem.

I guess i need to sic 'Code Enforcement' on it.

Bob Filipiak

[Richard Bassett]

The "Error link" from Reports or Updates gets called in situations such as the Primary file on LU1 being invalid.

Uh oh, could you clarify what 'invalid' actually meant in the context you tested?
Also a question - do you know if this still applies when there's a database transaction extant - ie. there _ought_ to be a rollback?

Thx

Edited by Richard Bassett, 22 June 2005 - 05:54 PM.

[Chris Pepper]

Created an update Function. L mode on a single standard sequential file.
Set Exit link to @MAIN and Error link to @SYSLOOK.

Used ALIAS to point to a file I knew existed... exit to @MAIN
Changed ALIAS to point to a file I knew did not exist... exit to @SYSLOOK

If I get time tomorrow I could try running on Oracle - not sure what to try though... trying to access a non-existant Table? This wouldn't have anything to roll-back, so it have to be a table nested somewhere down the Function. I'm not sure about whether I predict this to occur. Failure to read primary file in first LU is the only thing I'm confident will cause it!

[Matthews Estrice]

Hi everyone,

Same problem,'018 - error in writing file - TempFile'
@SYSERRTEXT - Error while excuting the query'
ERROR : current transaction is aborted , commands ignored until end of transaction block.

This is only a PROIV File browser time.
Neil Hunter what did you do?

Any help?

Thanks in advance ,
Matthews Estrice

[Neil Hunter]

Hi everyone,

Same problem,'018 - error in writing file - TempFile'
@SYSERRTEXT - Error while excuting the query'
ERROR : current transaction is aborted , commands ignored until end of transaction block.

This is only a PROIV File browser time.
Neil Hunter what did you do?

Any help?

Thanks in advance ,
Matthews Estrice

Why not recreate the browser?

Is TempFile a SEQ file?