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 modifier
script 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.

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) 

Run FCScan? (y/N)  

Run PSSWINFP? (y/N)  

(The (obvious?) assumptions are "modtempl" is the name of the modifying
script and "sctempl" the SYSCONF template.)

The "(y/N)" notation indicates that "N" is the default answer.  Only
lowercase "y" or uppercase "n" (or return/enter) are acceptable responses.

If modtempl is run without any command-line parameters, the help text will
be displayed:

:modtempl

MODTEMPL < template > newfile
              req.     opt.

MODTEMPL is designed to accept the SysConf template
file as redirected input.  The template file is not streamable.
It must be modified (easily by this script) before it can be
used.  Ideally, 'newfile' will be specified on the command line
but that is not a requirement.

---
Donna Hofmeister
Allegro Consultants, Inc.
408-252-2330


> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
> Behalf Of James B. Byrne
> Sent: Friday, September 12, 2008 7:57 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] IKE recovery
> 
> On:    Thu, 11 Sep 2008 09:05:43 -0700, donna hofmeister
> <[log in to unmask]> wrote:
> 
> > in donna's opinion, ike or not, this job should be on any 3000 that
> > one cares about ever having to recover ;-)
> >
> > http://invent3k.external.hp.com/~MGR.GARVERIC/
> >
> > (hopefully invent3k is up.  if not, let me know...)          - d
> 
> I have an identically named job that performs a similar function,
> albeit
> in a much more rudimentary fashion, so I am interested in "upgrading"
> to a
> more comprehensive version.  However, my MPE CI scripting skills have
> not
> been exercised in over 5 years and I am running into a series of errors
> when I run the SYSCONF JOB from the reference site given above:
> 
> For example:
>  *** RESUME EXECUTION OF COMMANDS
>  :
>  :setvar _sc_dir  '/SYS/SYSCONF/'
>  :setvar _sc_file _sc_dir + 'conf.' + _sc_date
>  :if finfo(_sc_file,'exists')
>  *** EXPRESSION FALSE: COMMANDS IGNORED UNTIL MATCHING ELSEIF/ELSE
>  /ENDIF
>  :  purge !!_sc_file
>  :endif
>  *** RESUME EXECUTION OF COMMANDS
>  :
>  :build !!_sc_file;rec=-80,,f,ascii;disc=50000
>  build !_sc_file;rec=-80,,f,ascii;disc=50000
>        ^
> (93/832) Continue?
>  Invalid character in MPE file name. (CIERR 583)
>  :file list=!!_sc_file,old;acc=append
>  file list=!_sc_file,old;acc=append
>            ^
>  Invalid character in MPE file name. (CIERR 583)
>  :
> 
> 
> Now, I dimly recall issues surrounding double escaping of escape
> characters meant to be passed to dynamically constructed job and
> command
> files.  But I am in no position with respect to time to rediscover how
> to
> resolve this issue for myself.  Is there something simple that I have
> done
> or failed to do that is causing me to see this problem in a JOB file
> that
> presumably many others are executing reliably without error?
> 
> 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.
> 
> Regards,
> 
> * 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 *