BackPak H4.00 Troubleshooting and Messages Manual

Troubleshooting
19 BackPak H4.00 Troubleshooting & Messages
• SCSI connector is not fully seated in the receptacle on the BackBox or the
NonStop system (check that the plugs' jackscrews are fully screwed into the
standoffs and are not cross-threaded due to not being inserted straight. The
SCSI connector should not move if wiggled);
• Bent pins in one of the SCSI cable plugs (unplug and examine carefully with a
magnifying glass);
• VTC SCSI Emulator Service on the BackBox VTC has not been started (check
the Windows Services Manager);
• SCSI Target Driver has not been installed and started (check the Windows
Device Manager, activate Show Hidden Devices, and check under Non-Plug-
And-Play Devices);
• SCSI cable is bad (try substituting a known good cable if possible.)
For SCSI connections to S-series via a Bridge:
• Log in to the Bridge Web Console and verify that the Bridge initiator FC status
is "online". Troubleshoot if not.
• Validate that the SCSI cable(s) are connected to the correct NonStop
systems.
• Log in to the Bridge Web Console and Reboot System. Retry SCF START tape
drive.
• Troubleshoot SCSI cables.
$BBEXT EMS Extractor abend at startup
Just after the PackPak programs are installed or replaced, the first startup of BBEXT
might abend with errors such as:
- “Filter table conversion error: -17, File: $SYSTEM.BPAK.EMSFILT1”
- in EMS: “$BBEXT-F1001 Error 70 from second FILE_OPEN_ on EMSDIST”
The root cause of these errors is a security issue when EMSDIST is started for the
first time by BBEXT after the BackPak installation, EMSDIST and interprets the EMS
filter provided with BackPak: EMSFILT1. The exact security requirement is not yet
known.
A bypass is to run BBEXT in a different context that will avoid the security issue;
once this BBEXT startup is successful, stop BBEXT and restart it in the planned way.
This was a successful bypass at all customer sites reporting this kind of error.
To bypass security issues and obtain a first successful run:
• Start BBEXT by the OBEY file OEXT, not as a permanent application PROCESS
defined in SCF $ZZKRN.
Remember one cannot start by TACL a process with a process name that is
already configured in a $ZZKRN permanent application process - even if this
process is not running; you might have to change the process name $BBEXT
in OEXT.
• Execute OEXT with SUPER.SUPER.