HP3000-L Archives

February 2005, 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:
Brian Donaldson <[log in to unmask]>
Reply To:
Brian Donaldson <[log in to unmask]>
Date:
Sun, 20 Feb 2005 14:39:03 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (55 lines)
If you are doing it in a job stream you would do:

!FILE X=Y
!COMMENT
!# ANOTHER COMMENT
!EOJ
and so on....

If you are doing it in command file or a UDC do:

FILE X=Y
COMMENT
# ANOTHER COMMENT

(without the !)

HTH,
Brian.


On Sat, 19 Feb 2005 13:25:19 -0800, garys0210 <[log in to unmask]> wrote:

>Does the HP3000 MPE allow comments on script statements the way HP UNIX
does?
>Thank you for the help.
>
>HP UNIX does.  example:    LOCAL_FILE="mufeed.log"                # NAME
OF xxxx comment
>
>My present know comment format:
>example1:
>!#  this is a comment
>example 2:
> !comment  this is a comment
>
>MPE statement I have tried that failed:
>******   Failed TEST  1:
> :FILE mrm10001=tst10001      !comment test file
>                              ^
> Variable name not found in variable table. (CIWARN 8101)
>                        ^
> Invalid character in MPE file name. (CIERR 583)
> REMAINDER OF JOB FLUSHED.
>****** Failed TEST  2:
>:FILE mrm10001=tst10001      # comment test file
> ^
> Invalid character in MPE file name. (CIERR 583)
>
>
>* 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