How to rebuild the Netmaster IPLOG
Article ID: 123157
Updated On:
Products
Issue/Introduction
This document is intended to assist in repairing an IPLOG that is causing problems.
It may be
- badlocked
- too large
- failing during an attempt to resize
- unreadable due to an excessive number of records
- corrupted
- on DASD where no space is available for extents
or need managing due to other issues.
This document does not supply error messages or details regarding various causes but provides guidance in getting the IPLOG back into operable condition in the shortest time possible.
The Netmaster IPLOG collects Connection events as designated in the Application Name Definitions (/IPAPPLS).
It utilizes a combination of SMF records and packet data to store these connections by IPaddress/Port and additional criteria .
Connection records are those written by the TCP/IP stack itself, and those are controlled by /IPAPPLS.
The IPLOG also collects FTP and Telnet events. These are taken from SMF records cut by the respective servers, combined with information from packet data and all connections are written to the long. They supply more application specific data than the connection records.
For all types of records, a maximum of 7 days of data can be stored.
Daily housekeeping deletes records older than the maximum designated.
/PARMS IPFILES is the parameter group where the IPLOG and maximum number of days is defined.
/PARMS IPEVENT determines what types of records will be written to the IPLOG and/or activity log.
Both have HELP screens that can be accessed using PF1 in case anything is unclear.
Because the data in this file is so transient, we recommend doing a DELETE / DEFINE and starting over with an empty file when problems occur unless you have a very specific need for the current data.
If the file seems corrupted and you want to try to repair it, see KB000052779.
Environment
Release: NetMaster Network Management for TCP/IP 12.2
Resolution
The IPLOG can be repaired while the region is active, or when it is stopped.
Steps for creating a new IPLOG on an Active Region
1. Logon to the Netmaster region and go to Command Entry ( issue CMD from any screen) and issue the following commands,
waiting until each completes before entering the next. This will remove the IPLOG from the region.
- NDB STOP IPLOG IMM
- UDBCTL CLOSE=IPLOG
- UNALLOC DD=IPLOG
2. OPTIONAL: If you do need to retain the data from the log, you can REPRO it out to a flatfile prior to the delete/define, then REPRO it back in after. This step is
optional.
Sample JCL:
//JOBCARD
// CREATE A NEW BACKUP DATASET,
// REPRO THE IPLOG CONTENTS TO IT
//
//COPYOUT EXEC PGM=IDCAMS
//SYSIN DD *
//* REPRO INFILE(DD1) OUTFILE(DD2)
//DD1 DD DSN=hlq.IPLOG,DISP=SHR
//DD2 DD DSN=new.IPLOGSEQ,DISP=(NEW,CATLG),
// SPACE=(CYL,(500,100)),
// DCB=(RECFM=VB,LRECL=4096,BLKSIZE=23445),
// VOL=SER=XXXXXX,UNIT=SYSDA
//SYSPRINT DD SYSOUT=*
Please be sure to modify DSN, SPACE and the VOLSER/UNIT information as needed, or change to use SMS.
3. The IPLOG needs to be deleted and redefined using the original parameters as defined in S01LCALC with slight modifications for the method you need for the storage/management/data class (or VOLSER/UNIT) and adjusted for the number of records as needed.
If you still have your JCL library from the install, it is recommended to use that as it will already match your environment.
Sample parameters for Netmaster 12.1 and 12.2 (other releases have different parameters):
Be sure to update the jobcard, hlq and storage parameters to match your environment.
// JOBCARD
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE (hlq.IPLOG) CLUSTER
IF LASTCC = 8 THEN -
IF MAXCC LT 12 THEN -
SET MAXCC = 0
DEFINE CLUSTER (NAME(hlq.IPLOG) -
MGMTCLAS(mgtclas) - /* <-----------Modify or delete as needed
STORCLAS(storclas) - /* <-----------Modify or delete as needed
INDEXED -
RECORDS(40000 150000) - /* <----adjust to match your environment
SPEED -
SHAREOPTIONS(2 3) -
REUSE -
) -
DATA (NAME(hlq.IPLOG.D) -
CONTROLINTERVALSIZE(8192) -
RECORDSIZE(815 8185) -
FREESPACE(5 5) -
KEYS(50 0) -
) -
INDEX (NAME(hlq.IPLOG.I) -
CONTROLINTERVALSIZE(2048) -
)
//*
//
4. REPRO the file from step #1 back into the new IPLOG (optional).
Sample JCL:
Be sure to modify the jobcard, and DSNs.
// JOBCARD
//* REPRO THE BACKUP DATA INTO THE NEWLY-DEFINED IPLOG VSAM DATASET
//*
//COPYIN EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
REPRO INFILE(DD1) OUTFILE(DD2)
//DD1 DD DSN=new.IPLOGSEQ,DISP=SHR
//DD2 DD DSN=hlq.IPLOG,DISP=OLD
5. Now it's time to reactivate the IPLOG.
In your Netmaster region, go to /PARMS and select parameter group IPFILES with option U (Update)
PF6 to action the parameter group.
It should take a moment, then come back with the message that the action was successful.
6. PF5 to view the ILOG for the parameter group.
It should show many lines of information with the current timestamp indicating that the IPLOG is now available.
7. Check the IPLOG by going to /IPHIST and viewing a section where you know records are being written.
Depending whether this is a test or PROD region, you may see immediate results or it may take a few minutes before new records are written.
Steps for Repairing the IPLOG on a Stopped Region
The steps here are very similar to those above.
1. Stop your Netmaster region with the command correct for your environment.
Standard here is /F NM,FSTOP
2. Wait until the job has ended; be aware of potential restarts if you have automation. Ensure it is not active for the Netmaster region.
3. Follow steps 2, 3 and 4 above to create an IPLOG containing data from the original log.
OR
Follow Step 3 only to allocate a new, empty IPLOG.
4. Restart the Netmaster region using the command that is standard for your environment.
The command here is /S NM
Feedback
