If you cannot find the answer to your problem here, please E-mail us by clicking 
Support@Kisco.com
and we'll respond as quickly
as possible. E-mail is checked regularly during normal business hours. Be sure to include a
reach
phone number with your message.
RBC/400 Problem Log
Problem Report Dated: 07/10/2000Affected release levels: RBC Release 4.04 and higher.
Problem Description:
When sending objects, the program fails with message CPF0001 in program SNDOSNDC.Problem Resolution:
This can happen if you experience a lot of transmission failures or transmission cancellations. To recover from this, please do the following:
Once the above is done, you should be able to use the object send commands.
- Issue the following series of commands:
RMVICFDEVE FILE(RXLIBR/SNDOICFA) PGMDEV(PGMDEVA)
RMVICFDEVE FILE(RXLIBR/SNDOICFB) PGMDEV(PGMDEVA)
RMVICFDEVE FILE(RXLIBR/SNDOICFC) PGMDEV(PGMDEVA)
RMVICFDEVE FILE(RXLIBR/SNDOICFD) PGMDEV(PGMDEVA)
RMVICFDEVE FILE(RXLIBR/SNDOICFE) PGMDEV(PGMDEVA)
Some of these may end with an error, that is OK.
- Issue the following command:
CHGDTAARA DTAARA(RXLIBR/RXDEVS (1 5)) VALUE(' ')
Note that the value is five blanks.
Problem Report Dated: 11/13/98
Affected release levels: RBC Release 4.04 and higher.
Problem Description:
When receiving objects sent from another system, RBC fails with error message CPA0701. The joblog for the failed job points to a CPF0001 and CPD0078 error message preceding the CPA0701. The failure is in program SNDORCVC.Problem Resolution:
This problem can happen when several RBC transmissions end in error or are canceled. Resetting a data area in the RBC library named RXLIBR will correct the situation. To recover, stop all RBC activity on your system, the change the data area named RXDEVS so that the first 10 characters are all blanks. When the change is made, you can resume normal processing.Problem resolved on: 11/13/98
Problem Report Dated: 09/15/98
Affected release levels: RBC Release 4.04 and higher.
Problem Description:
When routing reports from a System/36 to an AS/400, the print job RXPRT on the AS/400 fails with error message CPF0006.Problem Resolution:
This problem is caused on machines with a heavy report routing volume running on newer, faster AS/400 models. It is particularly noticeable on RISC AS/400's that are receiving reports from an SSP Guest System/36 running on the same box. The problem is caused by timing. A fix is now available from us in the form of PTF package RBPTF004. Contact us by E-mail to request the PTF.Problem resolved on: 09/18/98
Problem Report Dated: 07/18/98
Affected release levels: RBC Release 4.06 and higher.
Problem Description:
When sending a report to a remote AS/400 using the same release level of the RBC/400 software, the report transmission hangs with status "ICFW". On the target machine, a job appears in subsystem QCMN that appears to be looping in status "DLW-5".Problem Resolution:
This problem can happen following a communications line failure and, under certain circumstances, immediately following an initial or update load of the RBC/400 software. When this happens, take the following corrective steps. DO NOT CANCEL ANY OF THE AFFECTED JOBS!Problem resolved on: 07/18/98
- On the TARGET system, put the job in subsystem QCMN on hold.
- On the TARGET system, process the following command from the command line:
ADDICFDEVE FILE(RXLIBR/PRTRICF) PGMDEV(PGMDEVB) RMTLOC(*REQUESTER)- On the TARGET system, release the job previously held in subsystem QCMN.
When you complete this procedure, RBC/400 print routing will resume normal operations.
Problem Report Dated: 06/26/98
Affected release levels: RBC Release 4.04 and higher.
Problem Description:
When running the RBC Log Print, the job fails with error code LBE7207.Problem Resolution:
The RBC Log Print requires that the RBC application library be in the current active library list for the job that is running the listing. You can work around this problem by adding the library, named RXLIBR, to the library list prior to selecting the menu option for the Log Report. Many installations add the library to the system user library list. We recommend that you do this.Problem resolved on: 06/26/98
Problem Report Dated: 06/03/98
Affected release levels: RBC Release 4.04 and higher when running under OS/400 V4R2M0.
Problem Description:
When sending a file using the RBCSNDF (RBC Send File) command from a system under V4R2 to a system running V3Rx, the file send fails with error codes CPF3236 and MCH1202 issued to the session joblog.Problem Resolution:
After checking with IBM Support Line, it was determined that this is a problem in IBM's FTS support under OS/400 V4R2. You must order and install IBM PTF SF46315 on your V4R2 system to correct for the problem. When the PTF is installed, the problem is resolved.Problem resolved on: 06/04/98
Problem Report Dated: 03/05/97
Affected release levels: RBC Release 4.08.
Problem Description:
Under certain conditions where more than two locations are sending reports to a single location simultaneously, a routing program may fail with an error message at the receiving machine. The failing program is PRTORCVC and it will fail with error message CPF7365. The report will not be printed at the remote site.Problem Resolution:
This problem can be fixed by ordering and installing RBC/400 PTF package RBPTF001. Return to the RBC Customer Support page and choose the link to the RBC/400 PTF page. Follow the instructions there for ordering the PTF package.Problem resolved on: 03/05/97You can locate your "lost" reports on the receiving system. They are stored as files in library RXLIBR. Each report will be in a separate file with a filename that starts with RR'. Follow the instructions in your manual under the heading "Recovering Print Files after communications failure". (In the Release 4.04 manual, this is on page 34.)
Problem Report Dated: 08/19/96
Affected release levels: Release 4.04 when installed on RISC-based systems
Problem Description:
Automatic print routing does not work. Everything appears to be setup correctly, but reports do not get sent to any remote systems using the automatic routing feature.Problem Resolution:
A data que created for RBC under a prior release is too small for OS/400 V3R6 and this is causing the automatic report routing to fail. The solution is to delete the existing data queue and then re-create it with a length factor of 128. Future versions of RBC will correct for this problem. RBC/400 versions created after August 21, 1996 will not be subject to this problem.Problem resolved on: 08/21/96
Problem Report Dated: 08/09/96
Affected release levels: All
Problem Description:
Customer reported that RBC appears to be leaving some work files behind in the application library named RXLIBR on an intermittent basis.Problem Resolution:
RBC leaves recovery work files behind when certain communications functions fail. These files can be used to recover information that may have been lost as a result of the communications failure.Problem resolved on: 08/10/96The work files can all be found in the RBC library named RXLIBR. There are three types of work files. Files with file names that start witht he letters RR' and followed by a series of numbers are print files. These can be recovered using the RBCPRT procedure described in the user's guide. The other two files have files names that start with the letters RBC' or RBF' and are also followed by a series of numbers in the file name. These files are left on the system when an object transfer fails due to a communications problem.
One of these two files is a standard IBM savefile (*SAVF). The objects in the transfer set are stored in this savefile and can be recovered using the OS/400 RSTOBJ command. Once any objects have been recovered, these files can be deleted from the system.
Problem Report Dated: 07/31/96
Affected release levels: All when used with an attached System/36
Problem Description:
Customer reported that job "RXPRT" failed with error message SYS3827 (Error on CL command) while attempting to process a print spool entry arriving from an attached System/36. The error message offered the 0 and 3 options. Taking the 0 option allowed the job to finish and the report was placed in the print spool file but it's attributes were not set correctly.Problem Resolution:
The customer was using the QRBC user profile as the default user in the QCMN communications subsystem. The QRBC user profile does not have spool change authority. The solution was to add the special authority *SPLCTL to the list of special authorities for the QRBC user profile. Once this was done, the problem ceased and all spool file attributes were set correctly.Problem resolved on: 07/31/96
Problem Report Dated: 07/16/96
Affected release levels: All when used with an attached System/36
Problem Description:
Customer reported an FTS-1035 error message when attempting to send a file from an AS/400 to a System/36 using the RXSF procedure (option #3 from the S36EE menu named RXMENU). File could not be transferred to the S/36 even though it appeared to be a normal file and was residing in the S36EE file library on the AS/400.Problem Resolution:
The file being sent turned out to be a Source Physical File. RBC does not support sending a SRC-PF to a System/36 unless it is one of the special S36EE SRC-PF files such as QS36SRC (for program source) or QS36PRC (for OCL procedures). The solution for the customer was to convert the file member into a PF format using the CPYF command. When running this command, the FMTOPT parameter must be set to the special value *CVTSRC. The resulting PF file can then be sent to the System/36. An alternative solution is to move the member into the S36EE special source file QS36SRC and then use the RXSL procedure (option #5 on the RXMENU) to send the member to the System/36.Problem resolved on: 07/16/96
Problem Report Dated: 06/19/96
Affected release levels: All
Problem Description:
Customer reported a typographical error in the README documentation for topic #15. The CHGDTAARA command noted does not work correctly as documented.Problem Resolution:
The length factor for the CHGDTAARA command should read 4'.Problem resolved on: 06/19/96
Return to RBC/400 Customer Support Page