RBC/400 Recent Updates

RBC/400 Recent Changes Log

Effective date: 03/12/98

All of the changes, enhancements and PTFs implemented in RBC/400 since Release 4 was originally introduced in June 1994 have now been consolidated into this new release. All the new features and capabilities of the product have also been incorporated into a full new release of the documentation manual.

Effective date: 01/31/98

RBC/400 has been enhanced to improve transmission time when several users are sending OS/400 objects between systems. Prior to this enhancement, transmission delays could occur due to program and object waits. These delays have now been eliminated.

This enhancement is available as PTF package RBPTF003. See the PTF page for further information and instructions for ordering the PTF.

Effective date: 12/06/96

Compatibility support was added to RBC/400 for report distribution and object distribution with earlier versions of RBC/400. This simplifies upgrading for current customers. As of Release 4.05, some functions, including report distribution and object distribution, could not be used with any earlier releases of RBC/400. This makes it difficult for customers who cannot easily update all systems to a new release at the same time.

With this change, you can tell RBC when a remote site is at a Release level that is lower than the level on your local system. This forces RBC to use the older methods for report distribution and object distribution when working with these locations. The advantages of the improved methods will not be realized until all sites are upgraded to the new release. Once all sites have been updated, you can begin to take advantage of the new improvements (see below).

Effective date: 11/26/96

RBC/400 now supports distribution of program updates remotely via the Internet. To use this feature, you must obtain RBC/400 Version 4.07 or greater from Kisco Information Systems and install it on your system(s). With this feature, you can receive program updates and fixes from Kisco via the Internet. Initially, you must request the update via an E-mail attached PC file. In the near future, we will be making these update packages available for direct download from our Website.

Effective date: 11/15/96

The report routing feature that allows you to send a spool file report to a remote system (the RBCSNDSPLF command) has been completely re-engineered. The new version uses 75% less computer resource and is correspondingly faster than the previous version of the software.

Effective date: 11/06/96

The feature that allows you to send any object or group of objects to a remote system (the RBCSNDOBJ command) has been completely re-engineered. The new version uses 70% less computer resource and is correspondingly faster than the previous version of the software.

Effective date: 10/04/96

Support has now been added to support sending reports between systems that have short print line lengths. Prior to this change, RBC only supported sending print files with a fixed line length of either 132 characters or 198 characters. The change implemented allows for any line length up to 198. The line length will now be correctly set at the receiving machine. This allows certain output reports to automatically format correctly on an IBM laser printer.

Effective date: 09/27/96

Support for Command Prompting has been added to the remote command initiation feature. With this change, when preparing to issue any OS/400 command at the remote site, the command prompter can be used to simplify and edit for command validity before issuing the request.

Effective date: 06/20/96

Support has been added to show the originating userid on spool file entries received from any remote System/36. Until now, you could not determine the originating user after the report was transferred from your S/36 to your AS/400. With this change, the originating userid will show in the AS/400 spool entry in the USRDTA field.

Effective date: 03/04/96

The current version of RBC/400 is now in RISC-ready condition. This version can now be loaded and used on with a RISC or a CISC based AS/400 system. When installed on a CISC system, it can be migrated to the RISC system when the time comes. If the customer chooses to remove program observability to conserve disk space, then the original installation media must be retained in order to upgrade to a RISC processor.