. Kisco Home : products : SafeNet/400 : Support : Problem Reports .
.

SafeNet/400 Problem Reports

Last Updated: March 18, 2010
The following is a list of reported problems about SafeNet/400. If you have a problem that is not covered here, ask us via E-mail and we'll answer your question.

Register yourE-mail address and receive automatic notification when any of the SafeNet/400 customer support pages are updated.

SafeNet/400 Problem Reports

Index:

SafeNet/400 Release Independent Problem Reports:

SafeNet/400 Release 8 Problem Reports:

SafeNet/400 Release 7 Problem Reports:

SafeNet/400 Release 6 Problem Reports:

SafeNet/400 Release Independent Problem Reports:

When trying to run Nav-Central, it starts OK but when I try to do anything, I get an error 1217 that refers to a CPF4101 error.

Our early documentation on Nav-Central appears to be inadequate in certain areas. To use Nav-Central, you must use a user profile that has access to all objects (*ALLOBJ). Also, the user profile must have the job description in the user profile set to SAFENET in library PCSECLIB. Lastly, the TCP/IP DDM server function must be active on your iSeries-AS/400 system. If it is not active, you can start it with the following command:

STRTCPSVR *DDM
When these items are taken into account, Nav-Central should work correctly.

After installing Nav-Cenral, I am getting the message "Code is missing on Server or is in Error" when I try to start it.

When using Nav-Central, the user profile that you log in with must have the following permission rules in SafeNet/400 before it can work:

Server Access:
Distributed Data Management - *DDM
Remote Command/Program Call - *RMTSRV
Obect Access:
Library PCSECLIB - Read authority for *ALL objects
Library PCSECDTA - All authority for *ALL objects
Library QSYS - Read authority for *ALL objects
Once this is set up, then you should be able to access Nav-Central functions.

I have created a PWRDWNCL program for pre-powerdown processing, but it does not appear to be working.

Several customers have reported this problem. With the Pre-powerdown exit point registered and the specified PWRDWNCL program in place in library QGPL, the program was never getting called. After several goarounds with IBM, we have found out that there are some specific situations where the pre-powerdown exit point will NOT get called, as follows:

  1. System is on aux. power
  2. IPLing an LPAR
  3. System is already in a restricted state
If your situation falls into one of these categories, then you should be prepared that the pre-powerdown program will not be called under these circumstances. Unfortunately, this is a restriction imposed within OS/400.
Following a power failure, the SAFEQ dataque in library PCSECLIB is damaged. How can I recover from this?

The SAFEQ dataque is critical to the proper working of SafeNet/400. If it gets damaged, for any reason, it must be deleted and immediately rebuilt. NOTE: When you delete the data queue, you may get errors from network applications until the new data queue is in place. You should consider doing this procedure at a time when little or no network activity is happening on your system.

There are two different procedures for this depending on the version of SafeNet/400 that you have installed. Check the library named PCSECLIB for a *PGM object named BLDSAFEQ. If this object exists, then use Procedure A. If it does not exist, then use Procedure B.

Procedure A

  1. Sign-on as a Security Officer.

  2. Issue the following command from the command line:

    CALL PGM(PCSECLIB/BLDSAFEQ)

  3. Check the batch job queue named SAFENET in library PCSECLIB and delete all jobs shown that are waiting to be run. After clearing it once, check it again to make sure it is still empty. Repeat this until no more jobs arrive in the job queue.

  4. Check the SAFELOGING subsystem for multiple SAFELOGING jobs running. If found, manually cancel them all. If an ALERTWATCH job is running, manually cancel that too.

  5. End the SAFELOGING subsystem using the ENDSBS command.

  6. Restart the normal SAFELOGING subsystem by running option #11 from the SN2 menu.
At this point, SafeNet/400 should resume normal processing. Note that at NO TIME during this procedure process should you run the option to end the SAFELOGING subsystem by selecting option #12 from the SN2 menu.
Procedure B
  1. Sign-on using the special SAFENET user profile, this will guarantee that the replacement dataque is owned by this profile.

  2. Check the batch job queue named SAFENET in library PCSECLIB and delete all jobs shown that are waiting to be run.

  3. Shut down SafeNet/400 logging by going to the SN2 menu and running option #12.

  4. Delete the dataque using the following command:

    DLTDTAQ DTAQ(PCSECLIB/SAFEQ)
  5. Immediately create a new dataque with the following command:

    CRTDTAQ DTAQ(PCSECLIB/SAFEQ) MAXLEN(9000)
    SIZE(*MAX2GB) AUT(*USE)
  6. Restart SafeNet/400 logging by going to the SN2 menu and running option #11.
At this point, SafeNet/400 should resume normal processing.
When some of our Client Access user try to start a terminal emulation session, they are getting a "CWBUNPLA" error on their PC. We are also seeing SafeNet/400 rejections for the Remote Command server. Most of our PC users have no problem, this is only affecting certain users.

Several customers have reported this issue to us. We have been in touch with IBM on several occasions about it and are somewhat frustrated by what they are telling us. The Remote Command server is not supposed to be called during 5250 terminal emulation initiation. The CWBUNPLA error points, however, to an exit point problem but IBM has been unable to give us a satisfactory explanation as of yet.

The following is the latest information that we have from IBM concerning this problem:

Under some conditions (depending on the parts of Client Access installed on the client) the first connection to a 400 requires two calls to the remote command server. All subsequent 5250 starts will NOT call the command server. However, this is entirely dependant on the CA version installed, the OS version installed and the service pack level installed on the client. IBM cannot tell us which parts, versions or service packs cause this. Their response is, allow *PUBLIC access to the command server, limit the program call (objects) that can be access to only the following objects:
  1. QGY/QGYSETG
  2. QSYS/QSYRTUFI
  3. QSYS/QSYRTVFI
The following is a regerence to the IBM support website for more information:

http://www-1.ibm.com/servlet/support/manager?rs=0&rt=0
&org=as400&doc=B03C60533D594BEA86256A1D0076ABF7

The workaround solution for our customers is to activate *PUBLIC to the RMTSRV. If you do not have an unlimited user license, then each terminal user should be authorized to use RMTSRV. Then allow *PUBLIC (or each user) to access the two program objects.

Keep watch on this space for updated information about this problem. The above information is as of June 12, 2001.

SafeNet/400 Release 8 Problems:

SQL does not allow us to control the DROP PROCEDURE statement.

We have added this statement to the list of SQL statements that can be controlled by user profile. In addition, this release level also changes the deactivation process so that any user profile that is registered to SafeNet/400 as a Super Admin can run the deactivation. Also, a minor problem with the Executive Summary report is fixed to correctly count the number of members in the current archive file.

A PTF correction is now available to address this issue. It is in PTF package PCPTF881. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The On Line Transaction Review is not working on my system.

We recently did a complete re-engineering for the On Line Transaction Review (option #9 on the SN2 menu). We discovered that when you system is configured for a date format of either *YMD or *YDM, the process would fail. It has now been corrected.

A PTF correction is now available to address this issue. It is in PTF package PCPTF880. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Some remote commands are allowed to run when no rules are set up allowing them.

We found that certain command in the QSYS library were being allowed to run even though the user profile was not authorized to them. A recent PTF allowed this, but it is now corrected.

A PTF correction is now available to address this issue. It is in PTF package PCPTF879. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The joblog for our FTP jobs is missing information.

Based on a customer inquiry, we found that the exit program in SafeNet/400 for both the FTP Client and FTP Server functions was clearing the joblog periodically. This has been changed so that the joblog contents will be preserved.

A PTF correction is now available to address this issue. It is in PTF package PCPTF878. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

On-Line Transaction Review showing garbled data for Remove Execution Server.

A customer running i/OS 6.1 reported this problem to us. There is an apparent change in the way the OS handles CCSID information for this exit point. We have now updated SafeNet/400 to properly handle different CCSID information.

A PTF correction is now available to address both issues. It is in PTF package PCPTF877 which also includes a new feature. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Two important engineering changes made.

During normal operations, to improve general system performance, SafeNet/400 routes logging information through a data queue. This data queue is then processed by the jobs running in the SAFELOGING subsystem. However, some problems can crop up when the data queue fills up or becomes damaged. Prior to this change, the recovery process for this situation could cause problems for some customers. With this PTF, the recovery process has been strengthened and less intrusive.

Also, with the constant expansion of the use of SQL by client applications interacting with the System i, more and more complex SQL string constructs are presented to SafeNet/400 for processing. We have found that, sometimes, a completely new SQL construct will create a programming issue within SafeNet/400. To date, we have been quite successful at reacting to these new situations and issuing PTF corrections to the software, but these errors can create processing problems for our customers.

To alleviate this situation, we have made another engineering change to the SafeNet/400 software with this PTF. SafeNet/400 will now recognize when this happens and trap diagnostic information for the SafeNet/400 developers, but processing will continue without interruption. An operator notification is made so the customer can followup and address the issue.

A PTF correction is now available to address both issues. It is in PTF package PCPTF876 which also includes a new feature. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting an RNX0100/RNQ0100 error in program TRAPO6R.

This problem was reported by two customer, one while running the SafeNet/400 Security Report, the other while running the file purge process. We have now identified and corrected the root problem that was causing both issued.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF875. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am still having a problem with SQL after installing PCPTF873.

After issuing the PTF, we discovered that the fix was not correctly bound into one of the affected program objects. A fix for this has now been completed.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF874. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

SafeNet/400 is issuing a program error on a complex SQL statement.

We found that with certain comples SQL statements, SafeNet/400 could end with an index array error.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF873. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I received a CPF4101 error in the WRITETRAP program.

A customer reported this problem after having SafeNet/400 running without any issues for quite some time. We found that some code we had inserted to deal with an exception situation was failing when that exception condition was active. This is now corrected.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF872. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Seeing error message RNX0100/RNQ0100 from program SAFENET.

We discovered, based on information from a customer, that when a user submitted an incorrectly formed CHGSQLA command, this error could be issued. It is now corrected.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF869. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

A user access is being accepted, but we have set the profile up to always reject.

Based on a customer report, we found that when a user profile was set to R to reject transactions, but that same user was part of a group that was set to be accepted, including the public group, then the transaction was being accepted by SafeNet/400. We have now changed SafeNet/400 to conform to the documentation. This form of user profile rejection is rarely used by our customers.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF868. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The data queue server is issuing SafeNet/400 rejections, but there are no application issues being reported.

We have identified some applications in the OS that are passing blank data queue object names through the exit point data stream under certain rare circumstances. These are getting reported by SafeNet/400 as rejections. The product has now been changed to record these as accepted transactions so you will be able to see the transaction activity, but no rejection will be issued.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF867. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting rejections in DDM for objects and commands that are properly authorized in SafeNet/400.

IBM has been making changes to DDM code in the OS recently that have introduced a series of issues with the data stream being passed through the exit point. Some of these problems have been addressed through PTFs from IBM for the OS at various OS levels. Others were most easily fixed for our customers through a coding change to SafeNet/400. The problems all result for extraneous null characters (X'00') showing up in the exit point data stream as passed from the OS to SafeNet/400. On the error displays, these end up showing as blank characters.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF866. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When attempting an FTP session, I'm getting error code MCH0802 in a SafeNet/400 program.

There was a parameter mismatch in our program due to a recent unrelated program change. This has now been fixed.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF864. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When I update the email address for notification messages, it sometimes does not work.

and

I'm getting a rejection on an SQL CREATE that does not appear to be right.

We found a problem in the email address update process. It has now been corrected.

We found a parsing issue with the SQL CREATE verb when the LIKE option is used. This has also been corrected.

A PTF correction is now available to fix both of these problems. It is in PTF package PCPTF861. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When using FTP Client set to server level 4, I don't always get the right rules implementation.

and

SafeNet/400's automatic signon fails sometimes.

For the FTP Client issue, we found a problem in our implementation when used with long path names. The new PTF below corrects for this.

For the auto signon issue, we found that when used on a system with Kerberos implemented, the exit routine will sometimes return a bad value. We have now corrected for this issue.

A PTF correction is now available to fix both of these problems. It is in PTF package PCPTF860. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am unable to remove an active exit point from SafeNet/400.

and

The report process fails when I try to run the SQL Usage report.

We found that an incorrect version of a program needed for the exit point removal process was being distributed with new installs. Also, we found an artificial size restriction on the SQL Usage report when a very large report needed to be created.

A PTF correction is now available to fix both of these problems. It is in PTF package PCPTF859. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Program SAFENET is issuing a very intermittent error code of RNQ0121.

When a customer uses Supplemental Group Profiles and includes twelve or more of them on a single user profile, this problem could happen with the RNQ0121 error being issued. It could also be issued from the SAFENETC program. Both situations are now fixed.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF858. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When starting the On-Line Transaction Tester, I'm getting a program error.

We found that running the On-Line Transaction Tester following a completed migration of SafeNet/400 from the Release 7 level of installation, this feature could sometimes fail. We have now fixed it.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF857. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When viewing an SQL rejection, I tried to add authorization to a SELECT statement, but the user ended up authorized for ALL SQL statements.

We found that under certain circumstances, an incorrect SQL statement authorization could get generated when using the prompt from the rejection review process. This has now been fixed.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF856. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Error CPF5004 is being issued during the purge function.

When the purge was run on a system with a very large amount of history, and a report for all transactions was requested, we found that a CPF5004 message could be issued.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF855. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When I try to update an IP address from the On-Line Transaction Review, the command prompt comes up with an incorrect parameter value.

Also: Option 10 (the Executive Summary Report) on the INSTALL menu does not work.

Also: SafeNet/400 is generating errors when I use the new V 8.0 release of Showcase on my System i.

All of these issues were reported by current customers. In the first case, a recent change to the IP address registration changed the needed parameter value. In the second case, the correct command needed to run the option was missing from the menu. In the Showcase issue, some changes were made to the Showcase exit point that have now been provided for by SafeNet/400.

A PTF correction is now available to address all of these issues. It is in PTF package PCPTF854. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

SafeNet/400 is rejecting data queue server requests, but the object information appears to be missing.

We found that on some applications, the data queue server is now returning results with the object information left blank. We have updated the data queue server checking program so that it now passes these requests without posting an error code to the application.

A PTF correction is now available to fix this problem. It is in PTF package PCPTF853. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

A user profile is not showing up in the transaction history file.

Also: The Showcase exit point is not working following an upgrade to Showcase 8.0.

Both of these issues were reported by current customers. In the first case, when a user profile was coded with a value that was wholely contained by a super user profile, then the profile was getting treated as a super user. In the Showcase example, some changes were made to the Showcase exit point that have now been provided for by SafeNet/400.

A PTF correction is now available to address both of these issues. It is in PTF package PCPTF852. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When using the prompt to authorize a user for an SQL statement, sometimes the wrong SQL statement is set up.

When authorizing SQL statements using the F7 option from the rejection display, we found that on some occasions, an incorrect SQL statement was getting added for the user. This is now corrected so that only the specific SQL statement is added.

A PTF correction is now available to for this problem. It is found in PTF package PCPTF850. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF. Note: This PTF also includes several new features. Please check the updates section of this website for more information.

An SQL request is being accepted even though the object permissions do not permit it.

In the unusual situation where a *PUBLIC permission was given to all objects and permission at the individual profile level was restricted by an all object exclusion rule, we found that SQL was permitting the object access. This has now been corrected by processing the object level access permission in the correct sequence.

A PTF correction is now available to for this problem. It is found in PTF package PCPTF823. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The Security Report is showing rejections for objects in libraries QGL and QSYS but the On-Line Transactions Tester shows them as being accepted.

We found a difference between the edit routine being used for the report and that used for the On-Line Tester. The On-Line Tester was correct. This was due to a policy change made for the remote command server to accept calls to these two libraries for iSeries Access processing.

A PTF correction is now available to for this problem. It is found in PTF package PCPTF822. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting rejections in SafeNet that should work on the DATAQSRV server. The reason for rejection showing is "Rejected - Reason Unavailable".

Based on this customer's problem report, we found an issue that could cause this on an intermittent basis. It has now been corrected.

A PTF correction is now available to for this problem. It is found in PTF package PCPTF820. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Various Prolems including the following:

Object checking from the Showcase exit does not appear to be working correctly.

I am getting an MCH0603 when running the Print Object Useage Report.

When using the On-Line Transaction Tester, I'm having trouble finding my transaction.

Each of these issues were reported to us recently. For the Showcase error, we found that a parameter shift was happening with some calls from the Showcase exit program. We have now adjusted SafeNet/400 for this. For the MCH0603 error, we have changed the SQL parsing routine to prevent this from happening again. For the On-Line Transaction Tester, we have added time selection down to the millisecond level.

A PTF correction is now available to correct all of these issues. It is found in PTF package PCPTF819. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am seeing transactions recorded for a profile that is classified in SafeNet/400 as a super-user.

When we implemented the super-user feature in SafeNet/400, we never imagined that the FTP server would be needed by a super-user profile. We have since learned from our customers that this is not the case and have now implemented the super-user code for the FTP server exit point.

This PTF also includes corrections for several other minor issues including the purge (when run on a system with date format *DMY), the group profile lookup function and the program that removed users from the SafeNet/400 rules files.

A PTF correction is now available to correct all of these issues. It is found in PTF package PCPTF818. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When I run the purge process, it purges more than I requested.

For some customers who were submitting the purge directly to the job queue from a scheduler or from their own CL program, we found that the purge was purging all history up to the current day. This has now been corrected to use the submitted parameters. Purges run the from menu option were not affected and had been running correctly all along.

A PTF correction is now available to correct all of these issues. It is found in PTF package PCPTF817. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Error message MCH0603 is issued on SQL report.

We found that some customer SQL applications include bad characters in SQL strings that affect our SQL parsing process. We have now adjusted for this problem.

A PTF correction is now available to correct all of these issues. It is found in PTF package PCPTF816. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Variety of issues resolved - see details below.

The following issues were identified and have now been fixed for SafeNet/400 Release 8:

  • The TCP Signon Server was not getting properly authorized when done through a group profile reference.
  • The Showcase exit point was not always showing the transaction data on reports and display screens.
  • There were some intermittent SQL parsing issues with Showcase and other SQL processes.
  • Some of the *CMD objects in Release 8 did not have correct library references.

A PTF correction is now available to correct all of these issues. It is found in PTF package PCPTF815. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The Nav-Central interface will sometimes fail with MCH1210 in program CHKSYSCL.

On systems where the size of the transaction history file becomes quite large, we found that this program could fail as a result. It has now been fixed so that the failure no longer happens.

A PTF correction is now available to correct this problem. It is found in PTF package PCPTF814. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The PRTOBJUSG command is running to completion but not placing any records in the *OUTFILE specified.

We found a problem with this processing under SafeNet/400 Release 8. It has now been fixed.

A PTF correction is now available to correct this problem. It is found in PTF package PCPTF813. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Showcase is failing on my system.

A customer running SafeNet/400 Version 8 with Showcase 7.0 reported that sometimes their Showcase queries would fail because objects that were there could not be located. We have tracked the problem down to a library list specification change in Showcase. We have now modified our Showcase exit process to deal with this change so that this failure no longer happens.

A PTF correction is now available to correct this problem. It is found in PTF package PCPTF812. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The Alert notification job is failing on my system.

We found that customers who were running their systems with a default date format of YMD were getting this error. It has now been corrected along with another minor issue with the level 5 reset program.

A PTF correction is now available to correct this problem. It is found in PTF package PCPTF811. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

SafeNet/400 appears to be holding a large number of file locks.

Based on a customer report, we found where files were being left open in SafeNet/400 under the new Version 8 code. This has now been fixed with a resulting improvement in performance. We have also corrected an issue with the Showcase exit point with this PTF.

A PTF correction is now available to correct this problem. It is found in PTF package PCPTF810. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

We are seeing authority problems in some SafeNet/400 functions.

We found where these authority problems were being issued due to changes being made in the library list by certain SafeNet/400 routines. We have now modified the routines to make the library list changes using OS APIs and the authority problems have been resolved.

A PTF correction is now available to correct this problem. It is found in PTF package PCPTF809. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

SafeNet/400 Release 7 Problems:

I am getting intermittent MCH3402 errors in my SQL routine that trace back to SafeNet/400.

We have tracked this problem down and developed a fix for it. The MCH3402 is also sometimes accompanied by an RNX9998 error as well.

A PTF correction is now available to correct this problem. It is found in PTF package PCPTF736. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Some Super Trusted Users are not being recognized by SafeNet/400.

The Super Trusted User feature is documented as supporting up to 50 different user profiles. A customer that is using this feature extensively, reported that only the first 45 profiles were being recognized by SafeNet/400. We have now updated SafeNet/400 so that it works with all 50 profiles.

A PTF correction is now available to correct both of these problems. It is found in PTF package PCPTF735. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Various issues corrected, see details below.

We received customer reports for the following problems:

  • Unable to use the FTP command "CD" to point to the system's root directory.
  • MCH errors being issued from various CHKxxxx programs
  • MCH errors being issued from various PCCL0nQ program
Program changes have now been made to address these issue. A PTF correction is now available to correct both of these problems. It is found in PTF package PCPTF734. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

SafeNet/400 program P4RCS is reporting an index array error.

Under certain conditions, this program was failing with an index array error. In addition, another customer also reported a similar problem with reporting program TRAPO6R.

A PTF correction is now available to correct both of these problems. It is found in PTF package PCPTF733. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am seeing an index array error when attempting an FTP session.

A customer reported this issue to us and it has now been fixed.

A PTF correction is now available. It is found in PTF package PCPTF732. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Three customer problems corrected - see details.

Three separate problems were recently reported to us by different customers:

  1. FTP access continues to be logged even though the user profile is enrolled correctly as a super-trusted user.
  2. The CPYSNUSR command is not copying the SQL rules correctly for some users.
  3. The GETSEC program is issuing error CEE9901 with a reference to RNX9998 in the body of the message text.
Each of these issues has now been corrected. A PTF correction for all three is now available. It is found in PTF package PCPTF731. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

While processing an SQL client application, message CPF0804 is issued.

A few customers have reported this problem to us. We have traced it to SQL applications that are generated very long SQL strings for host processing. The CPF0804 message is accompanied by text that specifies "Built-in function operands not valid. Reason code 4." and points to a SafeNet/400 program with the name PCCL0nQ where n can be 1, 3 or 4.

A PTF correction for this problem is now available. It is found in PTF package PCPTF730. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When running the Object Utilization Report, the process sometimes hangs.

On very rare occasions, we found that certain client data recorded in the SafeNet/400 History Log could cause the Object Utilization report to hang.

A PTF correction for this problem is now available. It is found in PTF package PCPTF729. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Various issues corrected.

Based on customer reports, we have issued a corrective update fix for several minor issues reported in the following areas:

  • Errors being issued from the SAFENETU program in the operator message queue.
  • Corrections to the ADDUSRPTH processing program to record the correcth statement when selected from the update screen.
  • PCTESTR (option #9 on the SN2 menu) can fail when the data stream includes non-display characters.
  • When repeated attempts to log on using the FTP server are rejected, an error can be issued to the system operator message queue.
  • A problem was reported when the system could not find the USERS file.
  • The *ESCAPE message during deactivation/activation has been replaced with a *COMP message to avoid an error halt.

A PTF correction for all of these problems is now available. It is found in PTF package PCPTF728. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I'm running SafeNet/400 7.25 and still having problems with job switches in the FTP Client.

After issuing the fix package for SafeNet/400 7.25, we found one more location that still needed to be changed to preserve the job switch settings.

A PTF correction for this problem is now available. It is found in PTF package PCPTF727. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The joblogs from some network jobs are wrapping due to excessive entries coming from SafeNet/400.

A customer contacted us with this issue. We found some repetitive code that we could change that would significantly reduce the amount of information being recorded in the joblog.

A PTF correction for this problem is now available. It is found in PTF package PCPTF726. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF. Please note that this PTF also correct another issue, see the following item listed here.

I see many MCH0601 errors logged in a joblog from SafeNet/400.

While the MCH0601 errors have never caused any application failure, some customers reported that they thought it might be having a negative effect on system performance. We have now updated SafeNet/400 so that this message will no longer be issued from program PCCL01.

A PTF correction for this problem is now available. It is found in PTF package PCPTF726. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF. Please note that this PTF also correct another issue, see the previous item listed here.

While running an FTP Client application on our system, the job switches are getting changed in our CL programs.

When running FTP Client in batch within a CL program, a customer reported that their settings for job switch 1 was getting changed. We traced this to the SafeNet/400 exit program and have now changed the program to leave the customer's switch settings preserved.

A PTF correction for this problem is now available. It is found in PTF package PCPTF725. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When I run the On-line PC Tester, it will not accept the value *REXLOGON2 for the server filter.

A customer reported this problem and we found that certain server names would not process. It has now been fixed.

A PTF correction for this problem is now available. It is found in PTF package PCPTF724. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Certain SafeNet/400 operations appear inconsistent in the way the library list is handled.

Based on a customer request, we found several areas in SafeNet/400 where library list processing was not consistent across the product. This affected the NDB server and the TFR server (for older transfer processing).

A PTF correction for this problem is now available. It is found in PTF package PCPTF723. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

During normal network access, program P6SQL fails with error RNQ0121.

A customer based in Europe reported this problem. An alternate form of SQL CALL statement was found and we have modified our SQL parsing program now to look for it.

A PTF correction for this problem is now available. It is found in PTF package PCPTF722. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When running the User-to-Object Usage Summary, it fails with error RNQ0121.

A problem was discovered in the report program when working with unusually long SQL strings for this report.

A PTF correction for this problem is now available. It is found in PTF package PCPTF721. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

An SQL request is resulting in an incorrect object identified for security checking.

We found a problem with the SQL parsing under certain very unusual conditions. It has now been corrected with the PTF noted below. This PTF also includes several replacement *CMD objects to correct some OS/400 object security issues and it also contains some updates to the documentation.

A PTF correction for all of these issues is now available. It is found in PTF package PCPTF720. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The OS/400 file server is allowing transactions that should be rejected.

Based on a customer report, we discovered that if you had the OS/400 file server exit point set to level 3 (user-to-server control), then there were situations where a series of transactions could be authorized that should be rejected under certain specific situations.

A PTF correction for all of these issues is now available and we recommend that all customers install this PTF as soon as possible, especially if you are using level 3 controls on the OS/400 file server. It is found in PTF package PCPTF719. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Various problems with the DHCP server functions.

A customer reported several problems on their system when using SafeNet/400 with the OS/400 DHCP server. These included the following items:

  • The DHCP log files in SafeNet/400 were not configured for easy size growth.
  • CPF4101 was issued when running option #8 on the SN6 menu.
  • The SNDHCPPRG purge did not always run correctly.
  • Option #90 on the SN6 menu did not work.

A PTF correction for all of these issues is now available. It is found in PTF package PCPTF718. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

My system is issuing CPF0001 error messages referencing program SAFENETI.

This problem appears to be caused by several objects with incorrect security configurations within SafeNet/400. It only affects customers who are using the DHCP services from OS/400.

A PTF correction for this is now available. It is found in PTF package PCPTF717. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

SafeNet/400 is rejecting SQL statements that appear to be correct.

Based on a customer report, we have updated the SQL parsing program to improve selection criteria for certain unusual SQL statement formats.

A PTF correction for this is now available. It is found in PTF package PCPTF716. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

SafeNet/400 is not processing the right library/file from my SQL statement.

A customer reported this problem to us. After much investigation, we discovered that the customer was using SQL alias names that do not conform to the OS/400 library and file naming conventions. We have now adjusted SafeNet/400 to process these correctly, but a wildcard authorization is required.

A PTF correction for this is now available. It is found in PTF package PCPTF714. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The DHCP purge process does not appear to be removing all the information.

We found that one of the DHCP control files was not being updated when the DHCP purge was run. This has now been addressed and the purge is complete. This change also includes an update to the SafeNet/400 deactivation process to correct for an error message that can come up during the process.

A PTF correction for these issues is now available. It is found in PTF package PCPTF713. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

SQL "DROP PROCEDURE" statement not supported.

A customer reported to us that they wanted to control SQL "DROP PROCEDURE" statements by user profile. The current version of SafeNet/400 was ignoring the statements.

A PTF correction that now recognizes this SQL statement is now available. It is found in PTF package PCPTF712. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The Security Report seems to be missing some library names for a *NDB request.

On certain *NDB requests, we found that the Security Report (TRAPO6R) was dropping additional library names beyond the point where two libraries were shown. This has now been corrected to show all libraries in the request.

A PTF correction for this problem is now available. It is found in PTF package PCPTF711. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

An SQL request is generating an incorrect data rights rejection.

A customer reported the situation to us where an object was configured correctly in SafeNet/400, but a specific SQL request was still getting rejects due to incorrect data rights.

A PTF correction for this problem is now available. It is found in PTF package PCPTF709. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Two minor problems corrected.

Customers recently reported two minor problems to us. One involved running the SQL Useage Report; the report would occasionally fail due to a file size constraint problem. The other was an incorrect report heading showing on the Long Path Security Listing report.

A PTF correction for both of these is now available. It is found in PTF package PCPTF708. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Using the On-Line Transaction Tester, I am getting DDM rejections, but it looks like my configuration is correct and the transactions should be accepted.

We found a problem in SafeNet/400 where the On-Line Transaction Tester was returning a rejection notification on certain DDM transactions that really should have been accepted. When these transactions are run in real time, SafeNet/400 accepts them correctly.

A PTF correction for this is now available for these items. It is found in PTF package PCPTF707. This PTF also contains some new features. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Various minor issues, see details below.

Several customers contacted us recently with different minor issues. This include the following:

  • MCH0601 errors posted to the joblog for SQL requests.
  • Command parameters not allowing special DDM name location values.
  • SafeNet/400 is showing the Showcase point when it does not exist on the system.
  • SQL parsing issues under certain complex conditions.
  • DDM is allowing access which it should not when location controls are being used.

A PTF correction for this is now available for these items. It is found in PTF package PCPTF705. This PTF also contains some new features. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The NDB server is giving incorrect checking results.

A customer using the NDB server with an extensive list of library references reported this problem to us. It appeared as though SafeNet/400 was not doing the security checks in the sequence as documented in the user's guide.

A PTF correction for this is now available for these items. It is found in PTF package PCPTF703. This PTF also contains some new features. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Various minor problems.

Various minor problems have been reported to us concerning early copies of Release 7 that have been sent out. This PTF corrects the following items:

  1. All menus in SafeNet/400 have been updated to show the correct software release level at the top of the menu.
  2. The On-Line Transaction Tester program, option #10 on the SN2 menu, has been changed to fix a problem where slightly different results can be displayed when compared to the printed audit reports.
  3. The file server access program has been changed to correct a minor problem.

A PTF correction for this is now available for these items. It is found in PTF package PCPTF702. This PTF also contains some new features. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

SafeNet/400 Release 6 Problems:

We've been having problems with SQL statements since installing PTF 631.

After issuing the significant updates to SQL processing in PTF 631, a few customers reported problems processing certain complex SQL statements.

A PTF correction for this is now available for this problem. It is found in PTF package PCPTF633. This PTF also contains several other minor changes and fixes. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I have specified to control DDM by system name, but the history report is still showing user names.

We found several documentation conflicts in the way IBM shows how information is passed to the DDM exit points. This was causing this problem. We have now sorted out the exit point documentation and corrected the problem.

A PTF permanent correction for this is now available for this problem. It is found in PTF package PCPTF632. This PTF also contains changes to the SQL parsing routine. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting a RNQ0103 error when processing complex SQL strings through SafeNet/400.

Several customers reported this problem which resulted in a complete re-engineering of the network SQL parsing process in SafeNet/400. The new process, which is included in this PTF, is not only more accurate, but also is much more efficient than the prior version.

A PTF permanent correction for this is now available for this problem. It is found in PTF package PCPTF631. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting a CPF4101 error when trying to activate/deactivate SafeNet/400 on my system.

Based on a customer problem report, we found that this could happen when the activate/deactivate option was selected and the SafeNet/400 program library was not in the library list for the session. This is due to a recent change that was implemented in the product and is a new problem. As a workaround, you can simply add the library PCSECLIB to the session library list and the activate/deactivate option will run successfully.

A PTF permanent correction for this is now available for this problem. It is found in PTF package PCPTF630. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

After issuing a CHGPWD command, we are seeing library PCSECDTA in the session library list.

After reviewing the customer's information, we found that one of the SafeNet/400 exit programs was leaving a changed library list in place. The exit program has now been changed to leave the library list unchanged.

A PTF correction for this is now available for this problem. It is found in PTF package PCPTF629. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The WRITETRAP program in the SAFELOGING subsystem is issuing an MCH3601 error on an intermittent basis.

In certain circumstances, we were recommending to specific customers to reconfigure their SAFEQ dataqueue to a different length factor. We found that when we did this, the possibility existed that the WRITETRAP program in the SAFELOGING subsystem could abnormally end with a system error code of MCH3601. We have now corrected the failing program to adjust for this problem.

A PTF correction for this is now available for this problem. It is found in PTF package PCPTF629. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting a DDM rejection on a RTVDTAARA command but the object authorization appears to be correct.

Based on a customer problem report, we discovered a problem in the DDM validation routine that was not properly identifying the object to be checked. This has now been corrected.

A PTF correction for this is now available for this problem. It is found in PTF package PCPTF628. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

While using the On-Line Transaction Review, I sometimes get an RNQ1251 error.

A customer reported this problem to us. The RNQ1251 error happens when invalid data is presented to a display program. In this case, some invalid data was passed back to SafeNet/400 via the *DDM exit point. We have changed the display program now to avoid this error.

A PTF correction for this is now available for this problem. It is found in PTF package PCPTF626. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF. Note: This PTF also includes a new feature implementation.

A third party application caused the SAFENETA program to fail on a CPF180C error code.

A customer reported this problem to us. The CPF180C error happens when an OVRDBF is issued in a threadsafe job. The OVRDBF is not allowed in a threadsafe environement. We have now changed the SAFENETA program so that it is threadsafe compliant.

A PTF correction for this is now available for this problem. It is found in PTF package PCPTF625. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When I use the F6 function from the On-Line Transaction Review to author a new access rule, the prompt screen comes up with incorrect information.

A customer reported this problem to us. On investigating, we discovered that there was a problem formatting the new server permission prompt when the user profile exceeded 8 characters in length. User profiles of 8 characters or less were working OK.

A PTF correction for this is now available that will format the prompt correctly for all user profiles. It is found in PTF package PCPTF624. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting a CPF0001 when I try to deactivate SafeNet/400.

When running the process to deactivate SafeNet/400 on a system running OS/400 V5R2 can result in this error message. If you have this error, you can choose the option to ignore it and the deactivation will complete normally.

A PTF correction for this is now available that will prevent the error from happening. It is found in PTF package PCPTF623. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The SQL server is misinterpreting some information supplied in a query.

A customer reported that the SQL parsing routine was interpreting a field content selection as an SQL verb. This is corrected with this PTF. (See below).

I am getting a decimal data error associated with the DHCP server.

Under certain releases of OS/400, a decimal data error could occur when using the DHCP exit point. This is corrected with this PTF.

A PTF correction is now available for both of these problems. This PTF also implements a new feature which is documented in the "updates" section of the SafeNet/400 Customer Support section. The PTF package is PCPTF622. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I removed authority for an SQL user but SafeNet/400 is still authorizing requests for this user.

Based on a customer report, we found that under certain circumstances, the SQL server was not recognizing removed permissions.

A PTF correction for this is now available. It is found in PTF package PCPTF621 which also includes a new product feature. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting an MCH1202 error in program PCCL01H during DHCP processing.

We found a problem in the way the OS/400 exit point is returning information through the exit point. Non-conforming information is being returned and we have initiated a PMR with IBM about this. In the interim, we have modified our exit point process to address this error on a temporary basis until IBM issues a corrective PTF for OS/400.

This temporary correction is available in PTF package PCPTF619. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When using a MS join SQL selection, field names are being treated as if they are file object names.

A customer reported this problem to us and we have added code in our SQL parsing routine to deal with this situation. The following PTF has been issued as a correction. This PTF also includes a couple of other very minor changes to address an internal authority problem appearing in the DHCP exit points.

The problem has now been corrected and is available in PTF package PCPTF618. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When using Anonymous FTP, I cannot use UNIX style file naming.

We discovered some engineering changes in the FTP exit point when used on systems running OS/400 V5R1 or higher that are affecting this capability. We have now coded an fix for the problem that can be installed on OS/400 V5R1 and higher systems. If you install this fix on a system running OS/400 V4R5 or lower, the fix will be installed but not activated. When you upgrade to OS/400 V5R1, we can provide a procedure that you can use at that time to activate the PTF.

The problem has now been corrected and is available in PTF package PCPTF617. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

After installing SafeNet/400, I have some REXEC exit points where the level cannot be set.

On some systems running V5R1 or higher, we discovered that the exit point registration process could generate two extra REXEC exit points that are superfluous. These extra exit points create problems when using menu option #1 on the SN1 menu. The problem has now been corrected and is available in PTF package PCPTF615. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting error code RNQ0100 from program P4FIL.

We found that this problem was happening on a very intermittent basis for certain customers. It has now been corrected and is available in PTF package PCPTF614. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When using the On-Line Transaction Tester, I cannot specify the *FTPLOGON3 point.

On systems that do not use the US date format of MM-DD-YY, this was causing a problem. It has now been corrected and is available in PTF package PCPTF613. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

We are having problems with SQL command rejections and incorrect FTP rejections.

Some performance enhancement changes that we implemented with our PTF PCPTF604 are apparently causing some intermittent problems for customers on different release levels of OS/400. These problems are resulting in some SQL command rejections even though the command is properly authorized and some FTP rejections when the user appears to be properly set up. This problem has now been corrected and is available in PTF package PCPTF612. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

We get a CPF1834 message when the SAFELOGING subsystem starts up.

We found that on some machines, normally those with slower processors, the prestart job associated with the subsystem was starting before the subsystem initialization/startup process was complete. This problem has now been corrected and is available in PTF package PCPTF611. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When I choose to select a user for maintenance, and use the *ALLDFN option, some duplicate user entries are displayed.

While duplicate users were being displayed, we found that there were no duplicate users registered. This was simply a problem with the display program. This problem has now been corrected and is available in PTF package PCPTF610. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting a rejected SQL statement, even though the statment is authorized to the user.

We discovered a problem with SQL statement checking as a result of a recent PTF change. This problem has now been corrected and is available in PTF package PCPTF609. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I get an command error when attempting to use the new F6 function from the on-line transaction testing program.

When attempting to author a new access rule for the SQL statement "SET TRANSACTION", we discovered a problem with this new feature. This problem has now been corrected and is available in PTF package PCPTF608. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

When checking for file objects in the IFS, the wildcard character does not seem to be producing the right results.

While researching a problem reported by a customer, we discovered that the wildcard character was being processed incorrectly, producing results inconsistent with SafeNet/400 documentation. This problem has now been corrected and is available in PTF package PCPTF607. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

The powerdown program is not running even though it is registered according to SafeNet/400 documentation.

We have updated the pre-powerdown SafeNet/400 program to run as documented. This fix is available in PTF package PCPTF606. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

DHCP processing fails with errors TCP571D and CPF0001.

We found a missing program object on a customer's system and have decided to redistribute the missing object to all customers with SafeNet/400 Release 6 installed. This fix is available in PTF package PCPTF606. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

I am getting an error message RNQ0100 in an SQL program in SafeNet/400.

A customer reported intermittent problems with this error. After looking into it, we found a way to prevent them from happening. This fix is available in PTF package PCPTF605. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

Several minor fixes implemented

Several minor problems reported by customer have now been corrected. These include:

  • A fix to an IP address lookup routine
  • A correction to a data decimal error in the DHCP routines
  • A fix to PCSRVRS that had been causing an intermittent dump
  • Fixes to permit lower case DDM commands to be correctly interpretted
  • Changes to group profile checking that permit groups that start with a special character
  • The command SNDSVCFILE that was missing in some earlier versions of SafeNet/400 is now back in the library (used by Kisco for certain remote problem diagnostics)
These fixes are available in PTF package PCPTF604. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF. Customer's should be aware that this PTF contains new features along with these fixes and will require bringing your system to a restricted state for PTF installation.

I am getting an error message of CPF1892 issued from program PCCL04 which is related to Remote Command/Program Call server.

The problem has now been identified and corrected. The fix is available in PTF package PCPTF603. E-mail us and request the PTF package. All prior PTFs must be installed prior to installing this PTF.

During the upgrade from SafeNet/400 Release 5 to SafeNet/400 Release 6, I get a CPF0922 error message.

This problem only happens when you are upgrading from SafeNet/400 Release 5 to SafeNet/400 Release 6 on a system that is running OS/400 level V5R1 or higher. In the new OS/400 release, the error conditions for the ENDPJ command have changed and a new error condition (the CPF0922) is now possible.

To correct for the problem, just choose the ignore ( I') option to the error message when it happens. The installation process will continue correctly.

.
.
Kisco Information Systems 89 Church Street Saranac Lake, NY 12983
phone: 518.897.5002 | fax: 518.897.5003
sales@kisco.com about kisco kisco products product support kisco consulting services useful links