Specifications

Chapter 3. z/OS notes 45
example) must be the IP address of your z/OS TCP/IP. (It is not the IP address of the base
Linux in your zPDT system.) Port 1023 in the AD system is used for connection to Unix
System Services. This method of accessing Unix System Services is not adapted to 3270
terminals. It uses a basic UNIX-style terminal and vi, for example, can be used in this
mode.
3.12 SYS1.LOGREC full
Maintaining SYS1.LOGREC is a normal z/OS system programmer’s task. There is nothing
unique to the 1090 or the AD distribution. Production installations, using larger System z
machines, often keep ordered histories of LOGREC data and study any new material in
LOGREC. It includes data about hardware and software failures, IPL statistics, volume usage
statistics, and so forth.
Most 1090 users simply ignore SYS1.LOGREC until they receive messages that it is full.
These messages do no harm, but it is a good idea to clear LOGREC when such messages
are received. There is at least one job in the AD libraries to do this, but the job name (and
library name) may change from time to time. The following is a job to clear SYS1.LOGREC.
The particular format shown here is quite old and should be used exactly as shown.
//BILLCL JOB 1,OGDEN,MSGCLASS=X
// EXEC PGM=IFCEREP1,PARM='CARD'
//SERLOG DD DISP=SHR,DSN=SYS1.LOGREC
//DIRECTWK DD UNIT=SYSDA,SPACE=(CYL,5,,CONTIG)
//EREPPT DD SYSOUT=*,DCB=BLKSIZE=133
//ACCDEV DD DUMMY
//TOURIST DD SYSOUT=*,DCB=BLKSIZE=133
//SYSIN DD *
SYSUM
ACC=Y
ZERO=Y
/*
You may find slightly different jobs that perform the same function and any of these should be
acceptable. Never attempt to “clear” SYS1.LOGREC by simply deleting and reallocating it, or
by removing records with a text editor.
Note that you can edit IEASYSxx members (in PARMLIB) to say LOGREC=IGNORE to avoid
the LOGREC full problems.
3.13 Lost MVS console
MVS does not like to lose its operator console (and this is not unique to zPDT operation!). If
you accidently close the TN3270e session that contains the MVS operator console, you might
try the following recovery.
First, simply try to re-establish the session. This may be easier if the MVS console has an LU
name in the devmap. For example,
$ x3270 -port 3270 mstcon@localhost &
Depending on exactly what was happening when the console was lost, the TN3270e
connection to the aws3174 device manager may still be active and you cannot make a “new”