Re: INSTERR35 and 149 (214 Views)
Reply
Honored Contributor
Chuck Ciesinski
Posts: 830
Registered: ‎10-03-2000
Message 1 of 12 (211 Views)

INSTERR35 and 149

To all,

the saga continues, while doing an UPDATE, the AUTOINST process stopped after building SL,NL and XL with the following error (from console and INSTERRS.install).

INSTERR #35 Installer could not open AUTOGEN INSTALL.SYS
Non-existent permanent file (FSERR 52)
in recover block
patch selector internal error INSTERR 149
escape code = 40

PATCHAUD.PUB last entries,

Duplicate Patch for NST1
Duplicate Patch for NST2
Duplicate Patch for NST2
Duplicate Patch for NST4
Duplicate Patch for NST4

five blank lines to end of file at line 4038.

Since this is a test system, should I:
A. build autogen.install.sys (parameters unknown) similiar to to AUTOLOG as 1276b VA or
B. build similiar to AUTOHIST, 80b FA
C. Do a install and start over?

Please note that AUTOHIST, last lines..
JOB # p/f
IHFKXK2C.INSTALL.SYS J33 PASS
IHFKXN6A. " J34 PASS
IHFKXQ8C " J35 PASS
IHFKXT7B " J36 PASS

** PROCESS COMPLETED **
IN LINE 130

TIA,

Chuck
"Show me the $$$$$"
Please use plain text.
Honored Contributor
Chuck Ciesinski
Posts: 830
Registered: ‎10-03-2000
Message 2 of 12 (211 Views)

Re: INSTERR35 and 149

To all,

FYI, this is a 989 test going to 7.5.

Chuck
"Show me the $$$$$"
Please use plain text.
Honored Contributor
Kwan Fong, Emile
Posts: 1,162
Registered: ‎07-10-2000
Message 3 of 12 (211 Views)

Re: INSTERR35 and 149

Hello Chuck,

AUTOINST is involved; this must be a Powerpatch installation.

INSTERR #35, #149 errors generally occur when the A and F files from the PowerPatch tape have not been restored prior to run AUTOINST:

:FILE T;DEV=TAPE
:RESTORE *T;A@,F@;CREATE;SHOW;OLDDATE"

The safest way to proceed is as follows:

PURGEGROUP USL
PURGEGROUP UNL
PURGEGROUP UXL
PURGE HPINSTFL.INSTALL.SYS

Rerun AUTOINST.INSTALL.SYS and respond 'Y when it asks:

Should the installer resume with the previous installation?
King is the customer!
Please use plain text.
Honored Contributor
Chuck Ciesinski
Posts: 830
Registered: ‎10-03-2000
Message 4 of 12 (211 Views)

Re: INSTERR35 and 149

Yes,

Autoinst was used. I did an update, task level G, Option 3, FOS, SUBSYS, and PatchTape. I'll try your suggestion...

Chuck
"Show me the $$$$$"
Please use plain text.
Honored Contributor
Chuck Ciesinski
Posts: 830
Registered: ‎10-03-2000
Message 5 of 12 (211 Views)

Re: INSTERR35 and 149

Emile,

In following your instructions, there were approximately 30 files restored, including AUTOINST and the missing file. After purging the three groups and file, I ran Autoinst, the suggested dialog did not come up for resupmtion. So I started option 3 over again.
Watchinng the files come back on, again..

Chuck
"Show me the $$$$$"
Please use plain text.
Honored Contributor
Chuck Ciesinski
Posts: 830
Registered: ‎10-03-2000
Message 6 of 12 (211 Views)

Re: INSTERR35 and 149

Emile,

this time the restore of the FOS would not restore STRCNTL.NET.SYS, file in use. Tried manual restore, per error guide. No luck. REstarted agian as the file already on system, but started at restore of FOS. whne done, if still not correct, I'll log off and back on to restore the file then look at the AUTOHIST file to correct.

Chuck
"Show me the $$$$$"
Please use plain text.
Honored Contributor
Chuck Ciesinski
Posts: 830
Registered: ‎10-03-2000
Message 7 of 12 (211 Views)

Re: INSTERR35 and 149

Emile,
this system is headed for a complete install. I logged off and bacl on as manager.sys,install and the file is still in use.

Chuck
"Show me the $$$$$"
Please use plain text.
Trusted Contributor
Masatake Hanayama
Posts: 72
Registered: ‎12-23-1996
Message 8 of 12 (211 Views)

Re: INSTERR35 and 149

In most cases, STRCNTL.NET.SYS program starts when some user uses the
posix pipe "|"and never stops. Kill them with "kill" command in the
posix shell. The patch STRHDE1A text discusses this issue, though it
is related AUTOPAT, not AUTOINST.
Please use plain text.
Honored Contributor
Chuck Ciesinski
Posts: 830
Registered: ‎10-03-2000
Message 9 of 12 (211 Views)

Re: INSTERR35 and 149

Masatake,

After identifying 4 pins which had the file.

sh.hpbin
$ kill 154 -9
no process
$ kill 154
no process

through 28,29, and 154
all reported no process.

listf , 2 still showing * by filename.

Starting Install. wish me luck..

Chuck
"Show me the $$$$$"
Please use plain text.
Trusted Contributor
Masatake Hanayama
Posts: 72
Registered: ‎12-23-1996
Message 10 of 12 (211 Views)

Re: INSTERR35 and 149

The process id (PID) on the posix shell differs from the process id
number (PIN) on the MPE. Find out them with "ps" command on the posix
shell. And the "kill" command syntax is:
kill [-signal_number] [pid...]

:xeq sh.hpbin.sys "-L"
shell/iX> ps -ef
shell/iX> kill -9 nnnnn

One of the four processes should be the parent process of other
three processes, so when the parent has been killed, other child
processes may be automatically killed, too.

"It is important that the system is started with a
START NORECOVERY NOSYSSTART"
to prevent the STRCNTL program from startup by some reason.
Please use plain text.
Honored Contributor
Kwan Fong, Emile
Posts: 1,162
Registered: ‎07-10-2000
Message 11 of 12 (214 Views)

Re: INSTERR35 and 149

Hello Chuck,

Use :ABORTPROC PIN=;SYSTEM to kill the STRCNTL.NET.SYS processes.

STRCNTL is the program required for piping and I/O redirect to work. This program should automatically start when the system comes up. Since STRCNTL is a 'service', it is designed to run from NET.SYS. The file is flagged for access as long as the system is running.
King is the customer!
Please use plain text.
Honored Contributor
Chuck Ciesinski
Posts: 830
Registered: ‎10-03-2000
Message 12 of 12 (214 Views)

Re: INSTERR35 and 149

Emile and Masatake,

Little late guys. The full reinstall completed about midnight last night. Please note that when I ran sh.hpbin and did a ps -ef, the posix shell saw NO STRCNTL processes. That led me to go right to the Install...

Thanks for all your help and input. I'll remmeber for the next time...

Thanks,

Chuck
"Show me the $$$$$"
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation