HP3000-L Archives

March 2001, Week 4

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:
Tom Genute <[log in to unmask]>
Reply To:
Tom Genute <[log in to unmask]>
Date:
Tue, 27 Mar 2001 08:21:35 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (96 lines)
This will work with UDCs but command files are recommended.   I use UDCs
only for OPTION LOGON and for overriding systems commands, e.g., NEWGROUP,
STREAM, etc.   Unlike UDC'S command files do not load on logon and do not
require a SETCATALOG.   Therefore they require less logon overhead per
session and the commands are usually more easily modified, debugged, etc.
The downsides are that the command name is limited to MPE file naming
conventions (8 characters) and the file cannot be modified when opened.
The latter could be a possibility if the file contains prompts.

for debugging you can SETVAR HPCMDTRACE TRUE.   You can also SETVAR
HPAUTOCONT TRUE within the command files and handle error checking in the
script.   This would also go with SETVAR HPMSGFENCE 5 (set back to zero at
end).


file CALLER.CMD

INPUT Q1;PROMPT='Enter any value: '
echo !Q1 from !hpfile
SUB1
echo !Q1 !Q2 from !hpfile after calling sub
deletevar Q#

file SUB1

INPUT Q2:PROMPT='Enter a value into SUB1: '
ECHO !Q1, !Q2 from !hpfile

This is the screen display from executing CALLER.

:CALLER
Enter any value: BIG1
BIG1 from CALLER.CMD.SYS
Enter a value into SUB1: SMALLONE
BIG1, SMALLONE from SUB1.CMD.SYS
BIG1 SMALLONE from CALLER.CMD.SYS after calling sub


I keep all the command files segregated in their own group, rather than
cluttering up PUB.SYS or PUB of another account.   The "CMD" group requires
R,L,X access for anyone who will need to execute the commands.   The command
group does not have to be in the SYS account.  To set the path, the
following command is contained in the LOGON UDC.

comment set path to follow chgroup & include cmd.sys prior to pub.sys
 SETVAR HPPATH "!!hpgroup,pub,cmd.sys,pub.sys"


Tom Genute

>
> -----Original Message-----
> From: Andreas Schmidt [mailto:[log in to unmask]]
> Sent: Tuesday, March 27, 2001 4:24 AM
> To: [log in to unmask]
> Subject: Re: Subroutines on UDCs?
>
> do you have VESOFT ? STREAMX offers exactly what you're looking for!
> If you have MAESTRO this is also possible with MSTREAM.
> Best regards, Andreas Schmidt, CSC, Germany
>
>
>
>
> "Andres j. Ogayar" <[log in to unmask]>@RAVEN.UTC.EDU> on 27/03/2001
> 09:38:25 AM
> Please respond to [log in to unmask]
> Sent by:  HP-3000 Systems Discussion <[log in to unmask]>
>
> To: [log in to unmask]
> cc:
> Subject: [HP3000-L] Subroutines on UDCs?
>
>
> Please apologise if this is a FAQ, or a very naive question.
> We are implementing a not-so-simple UDC command which displays some
prompts,
> gets three or four values from the user, and, based on its input, streams
a
> job with these parameters.
> As you can think, this is a couple of hundreds lines of code, in some
files
> (on is the menu display, which is called some ties from the main routine,
> and so on).
> What I am looking for is some gosub..return (or procedure call; for the
> moment, value return is not necessary, but it will be a plus) mechanism on
> UDCs.
> Is there such a mechanism on the 3000s?
> Thanks in advance,
>
> -- Andres j. Ogayar
> -- Raytheon Microelectronics
> -- +34.95.224.92.27
>
> Please note my new e-mail address: [log in to unmask]

ATOM RSS1 RSS2