The following is a list of problems reported for iSecMap along with the solutions that we have developed for them. If you have a problem that is not covered here, ask us via E-mail and we'll address your problem.

Register your E-mail address and receive automatic notification when this page is updated.

iSecMap Problem Reports

Index:

iSecMap Release 2 Problem Reports:

• ISM 2.02: two fixes

iSecMap Release 1 Problem Reports:

• Problem reports resolved in release 1.03.
• New exit points added are not being properly identified.
• The ISECSET command (option 9 on the INSTALL menu) is failing.

iSecMap Release 2 Problems:

ISM 2.02: two fixes

1. When removing a path from IFS object tracking, lower case entry is now allowed. Prior to this, removing a path from object tracking was problematic.

2. A problem could happen if the optional message queue in the ISECSET settings was changed to *NONE. This is now fixed.

The fix for these issues is available as a PTF. This PTF can only be installed on a Release 2.01 version of iSecMap. The correction is available in PTF package ISPTF202. E-mail us and request the PTF package.

iSecMap Release 1 Problems:

Problem reports resolved in release 1.03.

• Problems with incorrect object level reporting have been fixed
• Errors being issued from file size limits have been fixed
• A file level check error has been corrected
• The list of libraries now shows which libraries are activated for tracking purposes on the list of libraries

The fix for these issues is available as a PTF. This PTF can only be installed on a Release 1.02 version of iSecMap. The correction is available in PTF package ISPTF103. E-mail us and request the PTF package.

New exit points added are not being properly identified.

When new exit points are added to the system, like during an OS version upgrade, they are not being properly identified in the software so that they can be acknowledged correctly. This has now been corrected. At the same time, a bug that could cause the monitor function to fail when more than one email address was used has also been fixed.

The fix for these issues is available as a PTF. This PTF can only be installed on a Release 1.01 version of iSecMap. The correction is available in PTF package ISPTF102. E-mail us and request the PTF package.

The ISECSET command (option 9 on the INSTALL menu) is failing.

When the ISECSET command was run with the special value of *NONE in the NOTIFY parameter, it was failing with an error message. This has now been fixed.

The fix for these issues is available as a PTF. This PTF can only be installed on a Release 1.00 version of iSecMap. The correction is available in PTF package ISPTF101. E-mail us and request the PTF package.