HP3000-L Archives

September 2008, Week 2

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:
"James B. Byrne" <[log in to unmask]>
Reply To:
James B. Byrne
Date:
Sat, 13 Sep 2008 13:21:07 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (72 lines)
On:    Fri, 12 Sep 2008 10:56:30 -0400, "James B. Byrne"
<[log in to unmask]>
>
> I read the readme file, and I am aware of the templating script.  Is my
> problem that the static SYSCONF JOB file is in fact depreciated?  Must one
> use the script to build a local SYSCONF JOB file?
>
> However, when I attempt to use the same job file as a template then my
> problem changes.  Now I get the error that too many parameters are being
> passed to the templating script:
>
> :file in=sysconft.jobtmpls.syslocal
> :file out=sysconf.jobs.syslocal
> :sysconfb *in *out
> sysconfb *in *out
>          ^
> Too many parameters were given for this command. (CIERR 10002)
> Supplied parameters do not match formal parameters. (CIERR 2039)
>
> I would love to get this to work.  Can anyone point out what I am doing
> wrong?  I have probably simply forgotten something basic.
>
On:    Fri, 12 Sep 2008 08:13:26 -0700, donna hofmeister
<[log in to unmask]> wrote
>
> 10/11/2005: (I) Converted the actual SYSCONF job into a template.
> Meaning that it is no longer a directly streamable file.  The template
> must be run through the "template modifier" script prior to use.  All
> that the modifierscript is doing is setting the true/false values for
> the three CI variables (documented above).  Typically, the script only
> needs to be used when then
> template is change.

es, as I indicate in my first message, I had already discovered that.

> Once you have the template version of SYSCONF and the "template
> modification" script on your MPE system (both saved as a normal,
> unnumbered 72-byte text files), you'll want to do something like:
>
> :file sysconf;rec=-72,,f,ascii;save	# sysconf doesn't already exist
> :modtempl < sctempl >*sysconf		# answer the following questions...
> Check Predictive? (y/N)

Yes, as shown above I do much the same thing, considering that
SYSCONF.JOBS.SYSLOCAL already exists.  However, this does not explain 
why, when I run the script, that I see this error:

> :file in=sysconft.jobtmpls.syslocal
> :file out=sysconf.jobs.syslocal
> :sysconfb *in *out
> sysconfb *in *out
>          ^
> Too many parameters were given for this command. (CIERR 10002)
> Supplied parameters do not match formal parameters. (CIERR 2039)
>

Can someone explain to me what is causing these errors.  I have named the
template processing command file sysconfb but have not modified any of its
contents.


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:[log in to unmask]
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2