Specifications

46 IBM System z Personal Development Tool: Volume 3 Additional Topics
connection to it. You can force the console session to completely disconnect by this command
in a Linux window:
$ awsmount 700 -d (assuming your MVS console is address 700)
You might then be able to connect the TN3270e session to address 700. You need to have the
TN3270e session connected before proceeding with additional recovery.
When MVS lost the console it may have started issuing messages in the Linux window used
to start zPDT. These are “HMC hardware console” messages. You can attempt to reactivate
the MVS console on 700 (assuming you have a TN3270e connection to 700) as follows:
$ oprmsg v 'cn(*),activate' (activate the "hardware console" for commands)
$ oprmsg v 700,offline
$ oprmsg v 700,offline,force (if the simple vary offline fails)
$ oprmsg v 700,online
$ oprmsg v 700,console
$ oprmsg v 'cn(*),deactivate' (optional)
This may not always work. Also, it may produce a console in 3270-2 (24 lines) mode, but this
is better than no console. The single quotes shown in the commands may be needed to
prevent the Linux shell from directly using the parenthesis characters in the commands.
3.14 Unable to start ISPF
When logging onto TSO, the following message is sometimes seen when attempting to start
ISPF:
%%% UNABLE TO ALLOCATE OR CREATE ISPF PROFILE DATASET
ISPF003 FOLLOWING FILE WAS NOT PREALLOCATED
ISPPROF
The most common reason for this problem is that the required ISPF profile data set was
uncataloged for some reason. The most common reason is attempting to use the same profile
data set from two different z/OS instances, such as in a Parallel Sysplex environment.
Crashing z/OS at just the wrong moment might also do this.
You need to recatalog the profile data set. Assuming you are logging on as IBMUSER, the
data set you want (in all recent AD-CD releases) is IBMUSER.ISPF.ISPPROF. You can logon
with another userid (ADCDMST is convenient for this purpose) and recatalog the data set.
The easiest way to recatalog the data set is to list the volume (ZDSYS1 or SCSYS1, for
example) using ISPF 3.4 and to use a C line command to catalog the data set. (The “C” is
entered at the beginning of the line for that data set in the ISPF 3.4 display.)
Another solution, after ISPF fails to start, is to preallocate the data set and then start ISPF
again. The TSO command to do this is:
READY alloc da('ibmuser.ispf.ispprof') f(ispprof) shr vol(zcsys1) unit(3390)
READY ispf (start ISPF again)
You need to use the volser that matches your current system, of course.