Problems running Autogen

[Ian Wood_1]

Trying to run autogen on a GS1280 VMS V7.3-2 with and get the following error
$ @sys$update:autogen getdata genparams feedback
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%DCL-I-SUPERSEDE, previous value of CLUE$DOSD_DEVICE has been superseded
%DCL-I-SUPERSEDE, previous value of CLUE$SITE_PROC has been superseded
%DCL-I-SUPERSEDE, previous value of CLUE$MAX_BLOCKS has been superseded
%SITEPAGSWP-I-DOSD, Mounting DOSD disks
Dump disk already mounted
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\FIRST_MESSAGE_SYS$OUTPUT\
%AUTOGEN-I-BADFILE, Bad versions of SYS$SYSTEM:SETPARAMS.DAT
and SYS$MANAGER:VMSIMAGES.DAT may
exist. We recommend that you delete all versions and start again.
%AUTOGEN-I-ERROR, GENPARAMS phase was aborted due to an unexpected error.
%SYSTEM-F-ABORT, abort

I've renamed both these files but still get this error, any ideas why?

[labadie_1 · Accepted solution]

autogen calls sys$update:agen$mail.com (if present) and any file indicated by agen$include in sys$system:modparams.dat. You should find the culprit there.

Good hunt

[Duncan Morris]

Hi Ian,

there has been an error detected by AUTOGEN, but the logic seems to have got a bit messed up.

The symbol FIRST_MESSAGE_SYS$OUTPUT should have been defined just after opening PARAMS.DAT

$file = "SYS$SYSTEM:PARAMS.DAT"
$OPEN/READ/ERROR=common_inerr params 'file'
$user_params = "FALSE"
$invalid_param_found = 0
$first_message = 0
$first_message_sys$output=0
$genparams10:

To find the real source of the problem which AUTOGEN was trying to report, switch on verification by doing

DEFINE AGEN$VERIFY "TRUE"

and rerun the AUTOGEN.

Once you have traced the problem and corrected it, you should switch off verification by deassigning the logical.

[Ian Miller.]

the error about FIRST_MESSAGE is a bug fixed by the VMS732_MANAGE-V0500 patch kit.

Check in SYS$MANAGER:SYCONFIG.COM as this is called by AUTOGEN

[Volker Halle]

Ian,

please also check your SYCONFIG.COM and any DCL procedures possibly called by that file.

You're using DOSD and some procedure re-defined some CLUE logicals as well and check the DOSD disk mount status.

Volker.

[Volker Halle]

To all,

in the past, it would have been VERY easy to find a solution for this kind of problem by googling for 'FIRST_MESSAGE_SYS$OUTPUT'

Even though VMS engineering has put the exact error message into the patch description text, Google does not find it, because the patch descriptions are not publicly available anymore (in the past they could be found on the Digital CSC Sydney patch server).

Volker.

[Ian Wood_1]

Commented out our include file and it worked, so have added the lines back in until I found the culprit. In the end it turned out to be GBLPAGFIL, changed this to be a MIN value and now all fine! Why it can't just tell you it doesn't like a particular value I don't know! Many thanks for everyone's help.

[Ian Wood_1]

Modified offending line and now okay....