TPU Functions Manual

[Robert Atkinson]

Anyone know which manual has the EVE functions in it.

Specifically, the 'eve$prompt_string' function and it's parameters.

I must have a printed copy of the manual somewhere, but I'm not sure which one it is.

Cheers, Rob.

[Wim Van den Wyngaert · Accepted solution]

Rob,

Try a search in sys$library:*.tpu for examples.

Wim

[Robert Atkinson]

Cheers Wilm - found the routine in eve$terminals.tpu.

Is there any documentation on which procedures get called in and how to use them.

I note the eve$prompt_string is documented in the TPU file, but there must be some proper documentation in the functions somewhere?

Rob.

[Wim Van den Wyngaert]

Rob,

I checked my documentation cd and found nothing. But I vaguely remember that something on paper existed around '87.

The sources of EVE are in sys$common:[syshlp.examples...]. There might be more text in it (sea *.tpu eve$prompt , proced /ma=and).

Wim

[Robert Atkinson]

The problem appears to go deeper. For instance, in this EVE$FILE code :-

eve$prompt_string (get_file_parameter, get_file_name,
message_text (EVE$_GETFILEPROMPT, 1),
message_text (EVE$_NOFILESPEC, 0)))

....the routine uses the GETFILEPROMPT and NOFILESPEC keywords, but I can't find any documentation anywhere that defines what these are.

I'll have a go at my VMs support company to see if they can help us shed light on this.

Rob.

[Wim Van den Wyngaert]

If you do a find in sys$message:tpumsg.exe for the texts, you will find the text that is used.

Wim

[Ian Miller.]

the documentation for tpu is here
http://h71000.www7.hp.com/doc/73final/6020/6020pro.html

[Ian Miller.]

and there is some info
http://h71000.www7.hp.com/doc/73final/6021/6021pro_020.html#tpu_evedo_app

[Robert Atkinson]

Wilm - searching through the TPUMSG file is not really an option, as it's compiled.

Ian - I've already read through those manuals, as well as the EVE reference guide, but I can't find any mention of the programming aspects I've referred to.

Rob.

[Wim Van den Wyngaert]

Found something but probably not what you are looking for.
http://vms.cc.wmich.edu/disk$openvms0731/000000/731final/6021/6021PRO.HTML

Good luck !

Wim

[Robert Atkinson]

As I said, I've been through the EVE manuals as well.

Got this response back from our support company, "I have been in touch with HP on this and they believe that the internal eve functions are not documented."

I'll keep chasing, but if anyone knows any different to this, please let me know.

Rob.

[Galen Tackett]

Rob Atkinson wrote:

>> ....the routine uses the GETFILEPROMPT and NOFILESPEC keywords, but I
>> can't find any documentation anywhere that defines what these are.

Rob,

Are these perhaps variables with string values instead of keywords? (Maybe you've already checked this out.)

[Bojan Nemec]

Galen,

As Wim mentioned the EVE$_GETFILEPROMPT and EVE$_NOFILESPEC are message codes which are in sys$message:tpumsg.exe. The TPU function message_text is like a wraper for the SYS$GETMSG system service which converts the message/status code in text.

Bojan

[Robert Atkinson]

Fair enough, but they are also predefined keywords that equate to static strings, i.e. EVE$_GETFILEPROMPT = "File to get:".

Is there a list of these anywhere?

[Bojan Nemec]

Rob,

The "File to get:" is defined in sys$message:tpumsg.exe. Try:

$ sea sys$message:tpumsg.exe GETFILEPROMPT /form=dump

Bojan

[Robert Atkinson]

I get :-

"direction. Go there? >FOUNDREVERSE'Found in reverse direction. Go there? &
I can see you're trying to help, but this isn't what I'd call a useful format.

Rob.

[Wim Van den Wyngaert]

Rob,

The problem is that most of the source files that contain the readable format of the messages (*.msg) are not delivered with VMS (IMHO they should). So, editing the file with EVE and finding the keyword is the best solution.

Wim

[Zeni B. Schleter]

On my OpenVMS v7.1 system the Eve$Prompt_Procedure is defined in SYS$COMMON:[SYSHLP.EXAMPLES]EVE$TERMINALS.TPU along with other procedures. The V7.1 doc set has an EVE manual and a DEC Text Processing Utility manual. V7.2 refers to the CD set. I looked for EVE$ anything in the Doc sets. It appears the EVE$Prompt_String is something that was added to EVE like "added value" procedures. Wasn't EVE itself a "value added" feature where TPU was the official software and EVE was given as an example.

- Zeni , 1st time response

PS. The Sys$examples:*.tpu are available on the v7.3-2 systems as well.

[Wim Van den Wyngaert]

Welcome Zeni,

EVE is indeed a layer on top of TPU. But only the external interface (UI) is documented, not the internal routines.

Wim

[Zeni B. Schleter]

rereading my message I left out the parameter definitions that are in the TPU file:
procedure eve$prompt_number ! Prompt for a number

(old_number,
new_number, prompt_string,
no_value_message)

! Procedure used by commands which prompt -
! for integers.
! Returns true if prompting worked or was -
! not needed, false otherwise.
!
! Parameters:
!
! old_number Old integer value - input
! new_number New integer value - output
! prompt_string Text of prompt - input
! no_value_message Message printed if -
! user hits Return to
! get out of the command - input

[Bojan Nemec]

Rob,

Attached is the TPUMSG file in ascii mode extracted from a VAX VMS 6.2 system with the UNMESSAGE facility. The EVE messages starts with the line:
.FACILITY EVE,548 /SYSTEM

Bojan

[Robert Atkinson]

Cheers Bojan.

This definitely covers one of my problems.

I'm going to speak to Hunter Goatley and see if it can be ported to Alpha/IA64 as well.

Rob.

[Bojan Nemec]

Rob,

As I know the UNMESSAGE was never ported to alpha. But, knowing VMS, I am sure that the information in this file was not radicaly changed when ported to alpha.

Bojan