Hi,
Hello, we installed Prognosis 11.7 on an HP-NonStop x86 server with Operating System L19.03.00 and when starting it gives us the following error:
-----
$OSS PRGN 33> run STARTPRG
Enter the process name for the Prognosis Process Manager (default $STM) ?
Checking Prognosis setup...
Setup detected a new Prognosis version.
Please use the command RUN IRCONFIG to configure Prognosis.
$OSS PRGN 34> RUN IRCONFIG
Customizing Prognosis for your system.
Enter the process name for the Prognosis Process Manager (default $STM) ?
Checking TCP/IP process information...
Please select the TCPIP names Prognosis should use to connect to your network.
Enter the process names or item numbers from the list below separated by spaces
or press enter to select the default list.
TCPIP Process Names (default $ZB018) ?
Enter the Prognosis TCP/IP port number (default 1960) ?
Prognosis comes configured with Trouble Shooting
and Capacity Planning database collections
Do you want to enable these database collections (Y/N) (default Y) ?
Checking COMMS configuration...
Finished customizing Prognosis for your system.
Saving AVAILABILITY Static Configuration...
Saving BASEMAN Static Configuration...
Saving COMMS Static Configuration...
Saving CONNEX Static Configuration...
Saving DISC Static Configuration...
Saving DISPMAN Static Configuration...
Saving EXTRACTOR Static Configuration...
Saving EVENT Static Configuration...
Saving EVENT_EXT Static Configuration...
Saving MQMANAGER Static Configuration...
Saving NETWORK Static Configuration...
Saving NODEGROUP Static Configuration...
Saving PASSWORDS Static Configuration...
Saving PATHWAY Static Configuration...
Saving PROGNOSIS Static Configuration...
Saving SECURITY Static Configuration...
Saving SCHEDULE Static Configuration...
Saving B24ATM Static Configuration...
Saving B24POS Static Configuration...
Warning: Unable to read Prognosis static configuration.
Saving TUNE Static Configuration...
Saving UPDOWN Static Configuration...
Saving B24EPS Static Configuration...
Saving ALERTS Static Configuration...
Configuring Prognosis...
Removing temporary files...
Merging configurations...
Updating COMMS configuration...
Copying OS dependent files ...
#SET sDSPMQPath [#fileinfo /volume/
^
Expecting a legal filename
Routine Trace:
disc^calc^mq8^cnf
^
update^cnf^mq8
^
setup^configure ALL NOUDEFS NOPARSE UNPACK SECURE
^
\DESA.$OSS.PRGN.IRCONFIG
^
$OSS PRGN 35>
------
Did we miss a step?
Thanks.
Williams Aspee
Solved! Go to Solution.
Solved by creating the file and running the installer
1.- FTP files.
2.- Create file (FUP CREATE DSPMQVER)
3.- Run Installer.
Thanks.
Williams Aspee
Hi,
I have just run the 11.8 patch program to install patch 3 and still have this issue. Running from the PRGNPTCH subvolume. Have put a DSPMQVER file in there priot to running the patch program and still had the error
Copying OS dependent files ...
Script Error!
[#if < 80
^
Expecting a constant
Or NOT
Or a string
(Badly formed variable name)
Or a number
Or (
Routine Trace:
update^cnf^mq8
^
setup^configure unpack copyos copymq secure
^
\MEL05.$OPSD00.PRGBPTMP.POSTINS
^
... done
CALAMITY - $Z55L.#S0: ERR 201
*ABEND*
Patch z1180p03 (in file z1180p3) was successfully applied
Just wondering whether the patch has been applied successfully?
Hi @ChrisBowring,
I'd recommend submitting a support case to investigate this if you can.
In general, the AUDITLOG file will provide you with the status of installed patches but, I suspect it'll just reflect the message shown at the end of the patch installation "Patch z1180p03 (in file z1180p3) was successfully applied" and you'll see something like:
11/12/2020 13:28:29 z1180p03 APPLY OK
This usually means it's applied OK but, given the error you observed, it might be safer for us to check and confirm.
If you can include a current irfax and pak the following files from your prgnptch subvol:
AUDITLOG
CATALOG
MANIFEST
PLOGP03
These should be all we need initially.
The CATALOG and MANIFEST files will allow us to check the current version of objects that have been applied and the patch log (PLOGPxx) may contain more details about what triggered the error.
It looks like a similar issue was addressed recently in the 11.8/11.9 installers and the same code change may just need to be ported into the irpatch utility. But the information mentioned above should help us confirm.
Regards,
Scott
Members | Likes |
---|---|
46 | |
13 | |
13 | |
12 | |
10 |