Release Notes for RSF and RSF-HA

Release 9.0

• New Change File While Active Function.  The new Change PF While Active (CHGPFRSF) command lets you change the layout of a physical file with minimal disruption. The file can be in use during the change, except for a brief time at the end when the new format is installed.
  
  For large files, using the system CHGPF or the ALTER TABLE commands to change a file layout is not always practical because these operations run for a long time during which the file is unavailable.
  
  The new CHGPFRSF command makes changing the layout of large files practical. The file format is changed in the background and all record and member changes made during the update process are preserved.
  
  This new feature is available in both the base and HA versions of RSF.

• Faster Role Swaps With Standby Journals.  Having a standby journal in place can speed up a role swap.  New options let you tell RSF whether to create and manage a standby journal for each library or IFS directory being replicated.
  
  Here's how it all fits together:

  • The local journal lives on the production machine where it constantly captures the changes to be replicated.

  • The remote journal lives on the backup (target) machine. Any changes that show up in the local journal are automatically mirrored to the remote journal. RSF uses the information in the remote journal to keep the target machine objects in sync.

  • The standby journal also lives on the target machine. Most of the time, the standby journal is not used and the the journal changes it collects are thrown away. However, if a role swap results in the target machine moving into production, the standby journal is ready to assume the role of the local journal.

  • Because the standby journal's main job is to take over as the local journal in the event of a role swap, the name and library of the standby journal on the target machine will match the name and library of the local journal on the production machine.

  • What saves time during a role swap is not just the existence of the standby journal, but the fact that journaling has already been started for all of the objects that will use the journal for  replication.

• New Delete Orphan Objects Tool.  The new Delete Orphan Objects (DLTOBJRSF) command makes it easy to delete objects in a library on the backup machine for which there is no corresponding object on the production machine.  When replicating non-journaled objects, deleting an object from the production machine does not always result in the automatic deletion of the corresponding object on the backup machine.  The new DLTOBJRSF command provides a convenient way to clean up those orphan objects.

• New Default Job Name.  When setting the sync attributes for a library, you can now specify the default job name to use when replicating the library in batch.  Previously, the job name was fixed.   Replication jobs for different libraries with similar names would end up with the same job name in batch.  Now, you can specify the exact job name to use when replicating any library.

• New Replication End Option.  The End Synchronization Job (ENDSYNCRSF) command has been enhanced, allowing you to choose whether to wait until the replication jobs have ended.  Previously, the ENDSYNCRSF command always returned control immediately while replication jobs completed in the background.  Now, you can request to wait until all of the specified replication jobs end.  This makes it easier to schedule another task which depends on all replication jobs having ended.

• Flexible Include Options.  When setting library synchronization attributes, you can specify objects to be included or omitted from replication.  Previously, there was no way to include all objects of a particular type.  This is now supported.  Specify INCLOBJ(*ALL  *DTAARA) to include all data areas, INCLOBJ(*ALL *USRSPC) to include all user spaces, and so on.  The default, as before, is to include all objects of all types.  This is now represented as INCLOBJ(*ALL  *ALL).

• Automatic Handling of Cross-Dependent Logicals.  When starting replication for a library, the entire library must be refreshed to ensure that both the source and target versions are identical.  To ensure that the library can restore properly onto the target, any existing library of the same name must first be cleared.  In the past, problems would arise when logical files in a different library were based on physical files in the library being refreshed, preventing the deletion of some physical files in the target library.  Now, RSF handles this situation automatically.  Any cross-dependent logicals on the target machine are deleted first and then restored to their original location after the library being refreshed has been restored.

• Automatic Target Release.  When sending objects from one machine to another, the objects may need to be saved from the source machine and restored onto the target machine.  If the machines are at different OS release levels, it's important to specify the correct target release when the objects are saved. 
  
  A new value of *AUTO is now the default for the target release (TGTRLS) parameter on all RSF SNDxxx commands.  *AUTO tells RSF to poll the target machine and determine the appropriate target release automatically.  For maximum efficiency, the polling is done once a day and the value determined is stored for future use.
  
  With this enhancement, RSF send functions can be used and coded in programs without having to change TGTRLS values as systems and OS release levels change.  RSF automatically detects the relative OS release levels and uses the appropriate TGTRLS value.

• New Options For Non-Journaled Objects.  When replicating a library, you can now specify whether to look for changes to non-journaled objects with the same frequency that journaling progress is checked.
  
  Only database files, data areas and data queues can be replicated with journaling. All other types of objects must be replicated using save/restore operations.  For large libraries, where nearly all of the objects are journaled, looking for changes to non-journaled objects less frequently can improve performance.

• Enhanced Spooled File Commands.  The Find Spooled File (FNDSPLFRSF) command lets you find one or more spooled files that contain a particular character string.  Now, you can specify the number of matching spooled files to find before presenting the list, allowing initial  results to be displayed more quickly.  On subsequent searches, you can indicate whether to start over or continue from where the last search left off.
  
  The Set Spooled File User Data (CHGSPLFRSF) command now runs much faster.  This command is used to set the user data for certain RSF job logs to a value that reflects the purpose of the job that created the log.

• New Command Checks IFS Include/Omit Specs.  Creating just the right generic specification to include or omit a subset of IFS objects can be tricky.  The new Is IFS Object Omitted? (CHKIOMTRSF) command lets you test your specifications with specific examples to be sure the results are what you intended.

• Easily Change All Sync Attributes Entries.  A new option on the Set Sync Attributes For a List (SETRSFSA) command makes it easy to change one or more attributes for all items in your sync attributes list.  Just specify the new special value of *ATTR for the LIST parameter.

• New Delete Journal Command.  Now you can easily delete a journal when it's no longer needed with the new Delete Journal (DLTJRNRSF) command.  Journaling is ended for all objects using the journal; any remote journals associated with the journal are detached; then, the journal and all associated receivers are deleted.

• Replicate SNADS Configuration.  When replicating system information, you can now include the SNADS data associated with the Work with Directory Entries (WRKDIRE) display.

• Faster Handling of Triggers and Constraints.  In a replication environment, trigger and constraint information is extracted periodically and saved in order to be ready for a role swap.  New options on the Extract Configuration Info (EXTCFGRSF) command make extracting and restoring trigger and constraint information much faster.  Previously, the information was extracted for all user libraries.  Now, you can specify that the information should only be extracted for libraries being replicated with journaling.

Release 8.6

↑

• Send Email and Text Messages.  New RSF commands make it easy to send email and text messages from any program or command line.  The Send Email (SNDEMLRSF) command lets you compose a message to multiple recipients, with optional attachments.  You can easily attach text files, save files and spooled files to your messages.  You can also send a brief note to any cell phone as a text message.
  
  Additional commands make it easy to attach OS/400 objects to your email messages on the fly.  Use the Email Library (EMLLIBRSF) command to send a library; use the Email Objects (EMLOBJRSF) command to send one or more library objects; use the Email IFS Objects (EMLIFSRSF) command to send IFS directories and objects; and use Work With Spooled Files - RSF (WRKSPLFRSF) to easily select and email spooled files.
  
  With Bug Busters' free InstallAid tool on the PC that receives the email, you can install attached OS/400 objects with just a few clicks.
  
  Configurable options make it easy to connect to the mail server of your choice.  Authentication and encryption are supported.

• The Machine Monitors Itself.  Can an IBM i attain consciousness?  Maybe not, but the newest RSF features bring it one step closer.  With this release we introduces the concept of conditions.  You can define conditions for whatever you like, tell RSF to monitor for those conditions and then have RSF take some action if one or more of the conditions is true. 
  
  For example, you could direct RSF to send an email to key people if:

  •  Any errors occur or items need attention within your High Availability environment.  Or,

  •  Errors occur in a particular user application.  Or,

  •  A particular job log shows up on an output queue.  Or,

  •  A particular message shows up on a message queue.  Or,

  •  Key system parameters--like CPU or disk utilization--exceed some threshold.

Because RSF lets you define your own conditions, the possibilities are endless.  To get you started, RSF provides flexible, predefined conditions that let you check for:

•  History log messages that meet certain criteria.

•  Message queue message that meet certain criteria.

•  Spooled files that match your specifications.

•  RSF-HA journal synchronization lag that exceeds some threshold.

•  RSF-HA replication status.

•  CPU or disk utilization that exceed some threshold.

Use the new Check Condition (CHKCDNRSF) to check the status of a condition.  Refer to source member CHKCDN in RSFTOOLS/QCLSRC for an example of checking conditions and taking action based on the results.

This new feature is particularly useful in a High Availability environment.  Being able to check your HA status from your iPhone is all well and good, but you still have to remember to check. Now, you can have the machine notify you if anything in your HA environment needs attention.  Meanwhile, you can concentrate on other things.

• Flexible Journal Management.  You can now specify how often RSF should change journal receivers for journals associated with High Availability/replication.  You can direct RSF to change receivers at each synchronization interval, once a day or only when the receiver size threshold is exceeded.
  
  In addition, you can now specify the number of days RSF should retain journal receivers no longer needed for replication, before they are deleted.  This makes it easier to share journals between RSF-HA and other applications while still keeping the receivers as small as possible.

• Library Display Enhanced.   The Display Library Size (DSPLIBRSF) command has been enhanced to show the number of objects in the library that could be journaled and the number of objects that should be journaled for replication.  This can be helpful in deciding whether to replicate a library with or without journaling.
  
  For example, a library containing only10 programs and 10 source files would show 10 objects that could be journaled and zero objects that should be journaled, since source files do not usually need to be journaled.

Release 8.5

↑

• Full Support for IPV6.  All RSF commands, options and functions have been updated to support the newest IP address formats for both outbound and inbound connections.  While IPV4 addresses of the form n.n.n.n (where n is a number from 0 to 255) are still supported, you can now specify addresses in the form x:x:x:x:x:x:x:x, where each x represents a two-byte hex value from 0000 to FFFF.  All valid IPV6 address specifications are supported, including replacing a series of zeros with a double colon ::.

• Role Swap Improvements.  Previously, a role swap had to be run from the system console.  Now, you can run a role swap in batch as well, eliminating the need to initiate the swap from a particular device. 
  
  Several types of virtual role swap are now supported as well, making it easier than ever to test your replication environment.  A virtual role swap is quicker than a full swap.  With a virtual role swap, the secondary machine is swapped into production, tests are run, data changes are made and then the machine is swapped back to the backup role.  At the end of the process, any changes made on the secondary machine during the virtual role swap are discarded.

• Same System Remote Journaling Now Supported.  For some time, RSF-HA allowed you to use remote journaling to transmit changes between two or more systems or partitions.  Now, the same remote journaling logic can be used when replicating from one library to another within the same partition.  This makes replicating within the same partition more efficient than ever.  As always, you can specify the type of replication journaling to use for each library and IFS directory.

• User-Defined Options Supported.  In addition to the pre-defined numeric options you can enter beside items in the Work With Sync Attributes list, you can now define your own PDM-like options for this display.  Sample options WJ (work with jobs associated with the item) and WS (work with spooled files associated with the item) are shipped with RSF.  All other RSF "Work With" displays support user-defined options as well.

• All in One.  New RSF-HA tools make it easy to perform certain functions for many items at once, where previously you were required to handle each item separately.   These tools reference the items you've defined previously in your Work With Sync Attributes list.  The Synchronize From Attributes (SYNCATTRSF) command allows you to start replication for all items in the list.  The Check Defined Items (CHKATTRSF) lets you compare source and target libraries/directories for each item in the list.  The Archive from Sync Attributes (ARCATTRSF) and Refresh from Sync Attributes (REFATTRSF) commands let your archive or refresh every item in your list.  Each command allows you to filter the list by generic name and server ID.  You can also omit specific libraries when running each command.

• New Tools for Managing Shared Journals.  RSF-HA can now manage journals that are shared by RSF and other applications.  RSF keeps the journals as small as possible, deleting old journal receivers when they are no longer needed by RSF or other registered applications.  A new API, RTVJRBRSF, is provided to allow an application to determine the name of the oldest journal receiver that it wants to keep on the system.  Special values make it easy to retain all journal receivers with entries newer than some date, or all journal entries for the last n days.  The Retrieve JRNRCV Boundary (RTVJRBRSF) command is used with the Change Sync Attributes (CHGRSFSA) command to tell RSF which journal receivers the application considers to be "in use."

• Improved Refresh Logic.  RSF-HA can automatically detect and repair errors that can occur in the course of replication.  When necessary (and when configured to do so) RSF will automatically refresh objects that get out of sync.  Now, RSF's refresh process is more efficient and more robust, resulting in fewer, faster refresh operations.

• Better Message Control.  You now have full control over the message queues to which RSF-HA run-time messages are sent.  While in the past, many messages were sent directly to QSYSOPR, you can now specify the target message queue for each replication job.

• IFS Flexibility.  A new option for IFS replication tells RSF to ignore errors that result from moving a object to a directory that doesn't exist on the target.  The classic example is moving an object from a replicated directory to /trash or something similar.  Typically, you don't want to replicate the /trash directory on the target.  With the new "Ignore Move Errors" option, the directory is replicated correctly, even if the /trash directory doesn't exist on the target machine.

• Clear Journals.  The Clear Journal (CLRJRNRSF) command allows you to clear all existing entries from a journal without deleting the journal itself or changing the journal status of objects using the journal.  Now, the CLRJRNRSF can be used to clear remote journals as well as local journals.

• New Command for Finding Spooled Files .  A new RSF command allows you to examine the body of spooled files and see a list of those that match your search string.  This command is ideal for finding a specific job log or any "needle" in the haystack of spooled files on your system.

• More Compression Options.  You can now specify four different levels of compression--*HIGH, *MEDIUM, *LOW and *NONE--when sending or archiving objects with RSF.  Higher compression saves space but can take more time to prepare.

• Updated Transmission Status.  RSF transmissions now show the average transmission speed in bits per second.  Status messages show the transmission rate while the transmission is in progress.  An informational message shows the average rate at the end of the transmission.

• Enhanced Server Export Tool.  The Export Server Entries (EXPRSFSRV) command has been enhanced to allow you to select entries by text as well as by generic name.  Now, you can select entries that do or do not contain specific words or characters in their text.  The EXPRSFSRV command is used with the Import Server Entries (IMPRSFSRV) command to copy RSF server directory entries from one system to another.

Release 8.4

↑

• New Compare Feature.  New commands allow you to compare libraries or IFS directories to determine if they match.  The items being compared can be on the same or different systems.  This new function provides an ideal way to confirm that backup copies and HA images actually match the originals.
  
  For a quick check, you can specify that only object attributes should be compared.  For a more thorough but longer running check, you can direct RSF to compare file data as well.
  
  Output to display, printer and *OUTFILE is supported.
  
  Compare entire libraries and directories, or compare subsets by object type and generic name.
  
  The Check Libraries (CHKLIBRSF) and Check IFS Directory (CHKDIRRSF) commands can be found on the new Integrity Tools Menu (GO RSFINT).  These functions can also be accessed from the Work With Sync Attributes display by keying option 16 beside any item.

• New Archive/Refresh Feature.  New commands allow you to archive and refresh libraries and IFS directories. These commands are collected on the new Integrity Tools Menu (GO RSFINT). The Archive Library (ARCLIBRSF) command takes a snapshot of a library and stores it in another library.  The Archive IFS Directory (ARCDIRRSF) performs a similar function for an IFS directory.  The resulting archive can be used in the future to restore the library or directory to the state that it had at the time the archive was created.
  
  You can use the archive/refresh functions to examine and manipulate a library or directory and then return it to its original state when finished. For example

  • Run test programs that use the library or directory.

  • Perform operations to validate a library or directory after a role swap.

When a library or directory is refreshed, changes made since the date/time it was archived are reversed. In particular:

• New objects are deleted.

• Missing objects are restored.

• Changed objects are restored to their archived state, including any changes to *PUBLIC or private authorities.

• New Options While Working With Sync Attributes.  From the Work With Sync Attributes display you can now

  • Key 14 beside any entry to work with the objects in the associated library or directory.

  • Key 16 beside any entry to compare the library or directory to its counterpart on the target machine.

  • Key F9 to work with active and waiting synchronization jobs.  A new "Sync Job Display Program" parameter on the Change RSF Defaults (CHGRSFDFT) command lets you customize how the F9 option works.

• Better Role Models.  Model role swap programs have been updated and enhanced to allow for

  • Better status messages, informing the user of where they are in the process.

  • Restartability. If interrupted or ended abnormally, the role swap will restart right where it left off.

  • Better archiving and importing of RSF settings needed for the role swap.

All in all, these changes make for a cleaner, easier, faster role swap.

• New Command to Clear a Journal.  A new Clear Journal (CLRJRNRSF) command is provided to allow you to easily delete all current entries for a journal.  RSF automatically keeps journals used for replication as small as possible.  But journals not managed by RSF or journals associated with libraries that are not currently being replicated occasionally need to be cleaned up.  This new command makes such journal cleanup easy.

• New Command to End All Subsystems.  The new End All Subsystems and Wait (ENDSBSRSF) command is provided for use in role swap programs.  The command will initiate the ending of all subsystems and not return control to your program until the system has reached a restricted state.

• Safety Checks.  A new check prevents you from trying to synchronize the entire IFS root directory, '/', thus preventing you from accidentally clobbering IBM internal objects.
  
  Another new feature prevents multiple copies of the same sync job from running simultaneously.  Different sync jobs for different libraries can continue to run simultaneously.

• Easier to End.  The End Synchronization Job (ENDSYNCRSF) command was changed to end sync jobs directly from the job queue rather than requiring that those jobs begin running before they can end.

• Default Job Names.  You can now associate a default batch job name with IFS sync attributes. Unlike libraries, where the default batch job name can be based on the library name, the best name to use when submitting an IFS sync job is harder for RSF to guess without your help.
  
  The commands that start a sync job now allow a value of *DFT for the batch job name.  For libraries, the default job name is S_nnnnnnnn, where nnnnnnnn is the first 8 characters of the library name.  For IFS directories, the default job name is taken from the IFS sync attributes.

• Live Long and Prosper.  To prevent network routers from dropping the connection prematurely, a "keep-alive" signal is now sent while RSF is waiting for the target machine to process data that was sent to it. 

• Remote Journal Name.  The remote journal name (as well as the remote journal library) can now be specified when using remote journaling.  Previously, the remote journal name was assumed to be the same as the local journal name.  Allowing for a different remote journal name is particularly useful when replicating libraries containing SQL packages as the system gives the same name to SQL journals in every library.

• Refreshing.  New sync attribute options let you specify the maximum number of objects with journal apply errors to refresh individually before giving up and refreshing the whole library or directory. You can also specify *NOMAX to insist that objects with errors are always refreshed individually and that the whole library/directory is never resent.  Previously, if more than 12 objects had journal apply errors in any one cycle, the entire library/directory was refreshed.
  
  Note that the new refresh threshold applies only to libraries and IFS directories using remote journaling.  When local journaling is used, a threshold of 12 is still assumed.
  
  In addition, new messages in the job log  indicate when an object is currently being refreshed.

Release 8.3

↑

• Remote Journaling.  Remote journaling is now supported for libraries and IFS directories.  Choose between remote and local journaling on a library-by-library and directory-by-directory basis simply by changing one option.  The rest is automatic.  All local and remote journals and journal receivers are created automatically by RSF.
  
  RSF starts a remote apply job automatically when synchronization is started for a library or directory that has remote journaling specified.
  
  Advantages of remote journaling:

  • The journal changes are sent more quickly and efficiently.

  • The journal changes are sent continuously and applied continuously.  At synchronization intervals, RSF checks the progress of the journal  apply process but does not need to send the journal entries.

Disadvantages of remote journaling:

• All journal entries are sent, even those that are not needed for replication.

• Filtering is not supported.  Changes will be applied on the target for all files being journaled.

• The source and target machines/partitions must be different; remote journaling cannot be used to replicate to the same machine/partition.

(HA version only.)

• Improved Status Display.  The Work With Sync Attributes (WRKRSFSA) display has been enhanced:

  • Highlight any items that are late reaching a synchronization boundary.  The time since the last sync point is compared to the default sync interval defined for the entry. If the time since the last sync point is greater than it should be, the entry is highlighted.

  • New options have been added for:

10=DSPJRN to display the journal associated with an entry.

12=WRKJRNA to work with the attributes for a journal associated with an entry.

18=Check Journal to determine the oldest receiver in use by RSF-HA for the journal associated with the entry.

• Replication Setup Commands.  Four new commands have been added to help with replication setup:

Display Cross-Lib Dependencies (DSPDBRRSF).  Use this command to display or print a list of files which have dependent files in a different library.  The classic case is a logical file in library A that is based on a physical file in library B.

Display Library Size (DSPLIBRSF).    Use this command to display or print a list of libraries in descending order by size.

Display Journaling Status (DSPJRNRSF).  Use this command to display or print the journaling status for one or more libraries. This is an easy way to see what journals are being used by what libraries.

Create Sync Subsystem (CRTSYNCSBS).  This command will create a subsystem and all related objects needed for running replication jobs efficiently.

• Flexible Sync Interval.  You can now change the synchronization interval on the fly.  New parameters on the Change Library Sync Attributes (CHGRSFSA), Change System Sync Attributes (CHGRSFSSA) and Change IFS Sync Attributes (CHGRSFISA) commands let you associate a synchronization interval with each item.  Then, specify *ATTR for the sync interval on the commands that start synchronization to get the sync interval from the attributes for the item being synchronized.  Changing the interval on the sync attributes will take effect at the next cycle;  no need to restart a synchronization job in order to change the interval.

• New Check Journal Usage Command.  The new Check Journal Usage (CHKJRNRSF) helps you determine the oldest journal receiver still in use by RSF-HA and the synchronization entry that is using it.  Run the command from any command line or key option 18 beside an item on the Work With Sync Attributes (WRKRSFSA) display.

• Additional Role Swap Model Programs.  Two new role swap model programs are provided to handle role swaps where the source and target IP addresses do not change.  See members SWAPTOBKP2 and SWAPTOPRD2 in RSFTOOLS/QCLSRC.

• Current Role Protection.  A new RSF default value lets you set the current replication role of the machine to *PROD, *BACKUP or *UNKNOWN.  Built-in protection now prevents swapping to the *BACKUP role unless the current role is *PROD, and to the *PROD role unless the current role is *BACKUP.

• Purge Error Log.  The new Purge Sync Log (PRGRSFSL) command makes it easy to selectively remove entries from the synchronization error log by date, type and more.

Release 8.2

↑

• Role Swap.  Perform role swaps efficiently and easily.  When mirroring is active, use a planned role swap to perform scheduled maintenance on the production machine while work is temporarily routed to the backup machine.  When you're ready, swap back.  When the production machine goes out of service unexpectedly, perform a role swap to route production work to the backup machine with minimal disruption.
  
  New commands, Role-Swap: Source to Target (SWAPTGTRSF) and Role-Swap: Target to Source (SWAPSRCRSF), make the process automatic.  User-written exit programs allow you to customize the process.  Sample exit programs are provided in RSFTOOLS.
  
  (HA version only.)

• IFS Mirroring.  You can now mirror IFS directories at the byte level.  Only those bytes that actually changed are sent to the target machine.  This greatly improves performance and flexibility when mirroring the IFS.  Any needed journals can be created automatically by RSF.
  
  Changes to the Synchronize IFS Directories (SYNCIFSRSF) command let you specify up to ten directories to mirror with one command.
  
  A new Change IFS Sync Attributes (CHGRSFISA) command allows you to specify attributes and options for IFS synchronization, including a list of objects to be omitted.

• Improved Select/Omit.  You can now specify a list of objects or generic objects to include when replicating a library, as well as a list of objects to omit.  This makes it easier to mirror a small subset of the objects in a library. 
  
  You can also tell RSF to filter replication journal entries on the source machine to ensure that only entries for included objects are sent to the target.

• Automatic Configuration.  If requested, RSF will create the journal library, journal receiver and journal for you automatically when journaling is needed.  Also if requested, RSF will set system values for you as needed to enable replication of user profiles and other system objects.

• New HA Menus.  The High Availability menus have been redesigned and improved.  Menu RSFHA now contains only those items that pertain to the source machine.  Items pertaining to the target machine are grouped on a new menu, RSFHAT.  The menus now contain more of the options frequently needed, grouped logically for ease of use.

• Expanded Sync Attributes Display.  The Work With Sync Attributes (WRKRSFSA) display now shows the replication status for IFS directories as well as for libraries and system information.

• Easier to Start Replication.  The new Start Synchronization (STRSYNCRSF) command makes it easier to start replication for your libraries, IFS directories and system information consistently.  A user-written exit program lets you tailor the way STRSYNCRSF works.  A sample exit program is provided in RSFTOOLS.  Now you can specify once which items you want to replicate, which jobs to submit, which job queues to use, etc. and STRSYNCRSF will do it the same way every time.

• Easier to End Replication.  The End Synchronization Job (ENDRSFSYNC) command has been enhanced.  You can now specify *ALL for job name to end all RSF synchronization jobs.  Non-RSF jobs are not effected.

• Replication Utility Commands.  Two new commands help you adjust your replication environment.  The Change User Profiles (CHGPRFRSF) command makes it easy to enable or disable many user profiles at once.  The Change PF Triggers (CHGTRGRSF) command makes it easy to enable or disable PF triggers for many files at once.

Release 8.1

↑

• High Availability Enhancements.  With RSF's High Availability feature you can now mirror changes to:

  • User profiles

  • System values

  • Network attributes

  • Authorization lists

  • Data queues

  • Object level authorities

  • Binary Large Objects (BLOBS) and Character Large Objects (CLOBS)

This is in addition to replicating database files, data areas, IFS objects, spooled files, message queues and other objects, which could be done with the previous release. In fact, there isn't much you can't replicate now with RSF.

Click here to read more about this feature.

New commands Change System Sync Attributes (CHGRSFSSA) and Synchronize System Info (SYNCSYSRSF) allow you to manage the synchronization of system objects such as user profiles, system values and authorization lists.

The new Work With Sync Attributes (WRKRSFSA) command provides a new interface to many of  RSF's HA functions.  From the WRKRSFSA display you can see the libraries and system information being synchronized as well as the latest status and error information.  You can also change synchronization attributes and start synchronization tasks from this display.

In addition, you can now create lists of libraries and system object types.  Then, use the new commands Set Sync Attributes From a List (SETRSFSA) and Synchronize List of Items (SYNCLSTRSF) to set the synchronization attributes for all items in the list and to submit synchronization jobs for each item in the list.  Source for these commands is included in RSFTOOLS.

Another new command, Display Sync Log (DSPRSFSL), lets you select and display synchronization errors, making  it easy to monitor synchronization tasks.

Finally, all of RSF's HA functions are now collected on a new High Availability menu.  Just key GO RSFHA to begin.

The RSF High Availability feature is optional and is licensed separately.

• Huge Spooled Files.  You can now send and retrieve huge spooled files.  The largest spooled file that could be transmitted previously was 16 megabytes.

Release 8.0

↑

• High Availability (Optional Feature).  New RSF commands Synchronize Libraries (SYNCLIBRSF) and Synchronize IFS Directories (SYNCIFSRSF) allow you to begin mirroring libraries and IFS directories in seconds. Changes are sent automatically to other systems, where mirror image libraries and IFS directories are maintained for high availability and recovery. Convenient options let you control which libraries and directories to mirror, which objects to omit, how often to synchronize, which systems to target, and more.
  
  RSF hides all of the communication complexities, allowing you to synchronize systems in the same room or half way around the world--whether connected by dial-up, LAN, SDLC, TCP/IP or the Internet.
  
  Database files are mirrored at the record level, and data areas are mirrored at the byte level.  All other object types are mirrored at the object level.
  
  Any needed journals are created and managed automatically by RSF.
  
  Two-way mirroring is supported, allowing different updates to occur to the same files on multiple systems while RSF keeps it all in sync.
  
  This RSF High Availability feature is optional and is licensed separately.
  
  Click here to read more about this feature.

• Copy an Entire System.  This new feature allows you to copy the entire contents of one iSeries system to another, unattended, without a tape drive.  Ideal for hardware upgrades and system exchanges.  A single command lets you copy every thing but the operating system¾from user profiles, libraries and IFS directories, to configuration objects and spooled files.  Options let you control exactly what gets copied.  You can even run the tool a second time to pick up objects changed since the initial copy was done.

• Remote Commands.  The new Run Command tool lets you run an arbitrary command on a remote system.

• Distribute Save Files.  New commands allow you to easily send and retrieve non-empty save files without saving them as objects first.  This saves time, space and machine cycles when your objective is simply to copy/move a save file from one machine to another.

• Spooled Files.  Enhancements to the Send/Retrieve Spooled Files commands allow you to send and retrieve large groups of spooled files, directing each to the same output queue on the target machine from which the file originally came.

Release 7.3

↑

• Super-Compressed Save Images.  The new RSF command Compare Save File Versions (CMPSAVFRSF) allows you to compare two save images and create a smaller difference file for distribution to remote systems. The compressed file is up to 70% smaller than the original save image, making it ideal for distributing large data sets to one or more remote systems. This new RSF function also provides an optimal way to get save images off site electronically.  Running the Build Save File Version (BLDSAVFRSF) command on the target machine allows you to reconstruct the newer save image from the previous version and the difference file. Both save files and the new virtual tape images are supported.

• Copy File Now Supports Lists.  You can now specify *LIST for the server ID on the Copy File Using RSF (CPYFRSF) command, allowing the file member to be easily copied to multiple targets.  *LIST is currently supported only in send mode, and only when using *SAVRST optimization.

• Send to Lists Simultaneously.  RSF commands which send ad hoc requests--Send Objects (SNDOBJRSF), Send Library (SNDLIBRSF), Send IFS Objects (SNDIFSRSF) and Copy File (CPYFRSF)--have been updated to create a temporary copy of the location list when sending to a list.  This allows multiple, simultaneous ad hoc requests to the same list.

• Requester Directory Recognizes Names.  Enhancements to the RSF Requester Directory now allow you to control access to your system by remote system name as well as by serial number.  You can now assign rights by the requesting machine's serial number, system name or both.  And, you can now set different rights for different partitions on the same machine.

• RSFSRV Not Changed on Upgrade.  The RSF install procedure and the Initialize RSF (INZRSF) command have been changed so that user profile RSFSRV is not automatically modified when you upgrade RSF.  Previously, the profile was reset to its default state, as shipped, when installing a new release of RSF.  Now, changes you make to special authorities and other profile options are preserved.

• More Relay Options.  RSF's relay logic has bee updated to send a message to the system operator if all distributions have not completed within a reasonable amount of time.  Possible replies to the message instruct RSF to continue waiting for additional minutes or to quit.

• Export/Import Server Entries.  Two new commands, Export Server Entries (EXPRSFSRV) and Import Server Entries (IMPRSFSRV),  allow you to export and import RSF server directory entries.  These can be used to copy one or more server entries from one machine to another.

• Retrieve OS/400 Release Function Enhanced.  The Retrieve Remote Release (RTVRSLRSF) command has been enhanced to support *LIST for server ID.  The value returned is the earliest OS release for all machines in the list.

Release 7.2

↑

• Broadcast Distribution.  With the introduction of Broadcast Distribution, this release takes large-scale iSeries object distribution to an exciting new level.  RSF's Broadcast Distribution offers large and midsized iSeries shops an elegant solution to that persistent problem: "How can you send software and data updates to hundreds of remote machines in a timely fashion?"
  
  With a single command, RSF 7.2 lets you send native objects, libraries or IFS objects from any iSeries to ten, fifty or even hundreds of other machines in about the time it would take to transmit to one of them.  RSF 7.2 also supports run-time encryption and compression to help make each transmission as safe and efficient as possible.
  
  The new broadcast features are based on the TCP/IP multicast protocol. On top of this, RSF adds integrity logic to help ensure that the entire transmission is received by all recipients. Receiving machines listen on a specific TCP/IP channel or group address. RSF transmissions on that channel are processed simultaneously by all machines that are listening. Meanwhile, the sending machine can track the progress of the transmission and report which machines have or have not received it.
  
  RSF Broadcasts can be sent over a LAN or a WAN, provided that multicast-capable routers and switches are used to build the network.

Broadcast Distribution vs. Relay Distribution

While Relay Distribution, introduced in a previous RSF release, offers an improvement over having a single machine send directly to each target machine, Relay Distribution still involves a separate transmission to each target machine, with all that this implies for total network traffic. Also, with Relay Distribution, the total time required to transmit to all intended recipients increases with the number of recipients, albeit at a slower rate than it would if transmitting to each recipient directly.

By contrast, with Broadcast Distribution, a single machine can send directly to an unlimited number of target machines simultaneously. The data transmitted only hits the network once but is received by all. This kind of transmission takes the same amount of time for 1, 10 or 1,000 recipients.  And, it doesn't clog the network in the process.

The payoff for Broadcast Transmission is more pronounced the more machines you are distributing to. For example, a national corporation that has an iSeries in each of its 800 branch offices can send out a nightly data update in 1/800th the time it might have taken previously. This is a big deal!

This does not mean that Relay Distribution is obsolete, however.  While Broadcast Distribution  can be used only over multicast-enabled TCP/IP networks, Relay Distribution will work over TCP/IP, SNA, and even a dialup networks.

• Tunneling.  RSF's new tunneling feature allows you to run any TCP/IP application through an RSF "tunnel".  The tunnel encapsulates the TCP/IP data stream and then presents it to the target server application unchanged.  This can have many advantages, including:
  
  Firewall Friendliness. A TCP/IP application such as telnet--which must connect to its own server on specific port on the target machine--can be routed through the RSF port, even though the application's server job continues to monitor its standard port.  On the server machine, the tunnel forwards the conversation from the RSF port to the application server port automatically. For a machine behind a firewall, this means that only the RSF port needs to be opened to allow both RSF data transmissions and other approved TCP/IP application connections to be received.
  
  Security. On the server machine, you can configure the types of RSF tunnel connections that are allowed and the target ports to which they may connect. You can also restrict tunnel access by requester machine serial number for a given target port.
  
  Encryption. RSF's *BASIC and *SSL encryption support can be used with any tunnel. Using telnet, for example, over an encrypted RSF tunnel allows you to run a completely secure iSeries (client)-to-iSeries (server) session, a feature which is currently available only through RSF.
  
  Idle Disconnect. You can set the maximum number of minutes that the connection may be idle before it is dropped. Using this feature with telnet allows you to automatically disconnect inactive sessions.

• Copy Files Between Machines Regardless of OS/400 Release Differences.  You can now choose whether RSF will use Distributed Data Management (DDM) or save/restore operations to copy database file members between machines.  Previously, DDM was not available with TCP/IP connections.
  
  The DDM option can be useful for copying file members between machines where the operating system release levels differ to the extent that save/restore is not supported.
  
  Where the operating systems levels of the machines are compatible, choosing the save/restore option can result in a faster transmission.

• Improved Transmission Performance.  New parameters have been added to the Change RSF Defaults (CHGRSFDFT) command to allow you to fine tune RSF's transmission performance over TCP/IP connections.  The new settings allow you to specify the block size and the TCP/IP send/receive buffer sizes to be in effect while sending or retrieving data with RSF.  Proper use of these setting may improve performance dramatically.  The actual results will depend on your network and on the settings chosen.

Release 7.1

↑

• Relay Distribution.  To address the needs of medium and large shops who must distribute objects to dozens, hundreds or even thousands of machines, RSF 7.1 introduces Relay Distribution. With this new feature, objects can be distributed to many machines in a fraction of the time it would take to distribute to each machine individually. Relay Distribution allows each receiving machine to become an additional sending machine, passing on the received objects to other machines known to it. In this way, the distributed package of objects cascades through the network, aided by an increasing number of helpers, each adding their CPU and communication resources to the task at hand. The machine that initiates the distribution maintains overall control.  RSF allows for multiple, redundant routes to each target machine while ensuring that only one copy of the distribution is delivered to each target.

• Fallback Connections.  Occasionally, the primary connection between two machines is down, but a secondary connection path is available. RSF 7.1 allows administrators to define a chain of secondary, or fallback, connections to use when the primary is unavailable. If the primary connection is a network or Internet connection, the first fallback connection might be a dialup link, or another network connection with a different IP address specified. Once the fallback connections are defined, the rest is automatic. RSF will attempt to complete any transmission using the primary connection. If the primary route is unavailable, the first fallback connection is tried, and so on. The net result is that more transmissions complete successfully, using the most efficient connection available at the time.

• Send to Multiple Locations With a Single Command.  With the newest release, all RSF "send" functions support lists of target locations, allowing administrators to send objects, libraries, file members and Integrated File System objects to a list of remote machines with a single command. Run-time compression and encryption are also supported.

• Full ASP Support.  RSF 7.1 includes full support for system and independent Auxiliary Storage Pools (ASP). With a single command, users can send objects to or retrieve objects from different ASPs on different machines.

• Automatically Calculate Target Release.  All RSF "send" commands now support a special value of *TARGET for the target release parameter.  When *TARGET is specified, RSF will query the actual release of the target machine.  If the OS/400 release of the target machine is greater than the release of the local machine, a value of *CURRENT is used. Otherwise, the actual release of the target machine is used.

• New Check RSF Connection Command.  A new Check RSF Connection (CHKRSFCNN) command can be used to determine if an RSF connection to another machine is currently active, or to wait until the connection becomes active.  The wait function can be useful if you want to run some RSF function only after the connection becomes available.

• Changes to STRRSFSRV Command.  A new parameter on the Start RSF Server (STRRSFSRV) command now makes it easy to set default preferences for which RSF server functions to start (SDLC, PPP, TCP/IP).  Parameters for starting and stopping OS/400 TCP/IP support have been removed.

• More Settings Preserved.  When installing a new release of RSF or using the Copy RSF Data (CPYRSFDTA) command to copy setting from a previous release, RSF now copies forward the job descriptions from the old release and preserves changes to default preferences specified on the Start RSF Server (STRRSFSRV) command.

• More Pass-Through Parameters.  Additional parameters have been added to the Start Pass-Through Using RSF (STRPASRSF) command to support remote password, password encryption, initial program, initial menu and current library on the target machine.  In addition, you can now specify a telnet port to use for TCP/IP connections in the RSF server directory entry.

• Send Larger Save Files.  RSF "send" functions have been enhanced to allow for sending save files with more than 10 million records.

• Message Forwarding.  Start Message Queue Monitor (STRRSFMSGM) command, which allows you to forward messages from satellite machines to a central machine, has been updated.  Header messages sent to the target machine now clearly indicate the system name from which the original message was forwarded.

Release 7.0

↑

• PPP Support.  This version of RSF includes support for dial-up TCP/IP connections using the PPP protocol.  All configuration--such as creating line descriptions and configuration profiles--is done automatically by RSF.  With this release, users can send and retrieve objects, libraries, spooled files and IFS objects over PPP connections.  Run-time compression and encryption are also supported.
  
  As a client, RSF 7.0 lets you connect, without prior configuration, to any TCP/IP server over a dial-up link.  Up to 256 simultaneous connections to different servers are supported.  RSF automatically selects an available line and modem when making new connections, and automatically shares an existing connection when two or more users contact the same server.
  
  As a server, RSF 7.0 supports up to 256 simultaneous inbound connections from an unlimited pool of potential clients.

• Dial-Back Support.  Dial-back support is included as part of RSF's PPP support.  With dial-back, one machine calls another, requests a call back and then hangs up and waits for the return call.  Any phone charges will accrue to the machine that was first called, rather than the one that initiated the transaction.  This feature allows developers and software vendors to support remote machines over a dial-up network, with each remote paying their own connection charges.

• Internal Modem Support.  RSF's new PPP support makes full use of the internal modems which are shipped with new iSeries machines.  A central machine can now easily support an unlimited network of remote iSeries using any combination of internal modems and externally attached async modems.

• PC Dial-In.  With RSF's PPP support, it's easy for PCs and other non iSeries clients to connect to your iSeries or AS/400 over a dial-up link.  Running one RSF command enables remote dial-in, while another command disables it.  CHAP password authorization is supported for maximum dial-up security.

• Uninstall Support.  New commands allow you to implement schemes for uninstalling previously installed packages.  Easily track pre- and co-requisites and ensure that packages are uninstalled in the proper order.

• Important Note:  This release of RSF requires a new authorization code.  If you are upgrading from a previous release of RSF, send an email listing your machine serial number to support@bugbusters.net requesting an authorization code for RSF 7.0.

Release 6.3

↑

• Run-Time Compression.  With RSF Version 6.3, Bug Busters has added run-time compression to all of the RSF TCP/IP distribution functions.  You can now compress data up to 70% when transmitting libraries, spooled files and IFS objects.
  
  Any objects compressed during transmission are automatically decompressed at the other end.  This means that the transmitted objects are identical to the original objects that were sent.  Aside from the fact that objects arrive more quickly at their destination, there is no way to tell that the objects were transmitted using compression.
  
  Compression is supported both when sending objects to other systems, and when retrieving objects from other systems.  New command parameters allow you to turn compression on or off for each transmission.
  
  Three levels of compression are supported, allowing administrators to optimize transmission performance for their specific environment.

Release 6.2

↑

• Enhanced Security.  Previously, the user profile and password for SDLC connections had to both be RSFSRV.  Even though the RSFSRV profile was  installed with limited authority, the requirement to use a known connection profile and password could present a security exposure in some circumstances. With this release, any profile and password may be used to connect.  New parameters on the RSF server directory entries allow connection profiles and passwords to be specified for each server.

• Send/Retrieve IFS Objects.  New commands SNDIFSRSF and RTVIFSRSF allow you to send and retrieve objects in the Integrated File System.  You can specify up to 15 generic path names.  Objects can be restored to the same or to different path names.

• User-Defined Options Supported on Work With Requesters Display.  User-defined options may now be keyed beside list items in the Work With Requesters display. This allows you to perform virtually any function for one or more requesters. User-defined options were previously supported only for the Work With Servers, Work With Packages, and Work With Catalog displays. 
  
  An additional user-defined option, "WL", is now shipped with RSF.  Keying "WL" beside an entry on the Work With Requesters display presents a list of RSF log entries generated by that requester.

• Pre/Co-Requisite Processing.  A new program is included in library RSFTOOLS to demonstrate how pre-requisite and co-requisite packages can easily be retrieved and installed as a part of the process of installing any individual package. The new program is called "REQUISITES". Source can be found in file RSFTOOLS/QCLSRC. 
  
  A new command, Install Pre-requisite (INLRSFREQ) is also provided to facilitate the installation of pre- and co-requisites.

• Send Package Command Enhanced.  With this release, you can use the SNDRSFPKG command to send a save file to another machine without defining an RSF package that refers to the save file. By specifying *SAVF for the package name and entering the qualified save file name, you can send ad hoc save files without having to define a package first.

Release 6.1

↑

• Improved Support For Fix Distribution.  This release contains several enhancements that make it easier than ever to distribute program fixes with RSF.

  • A new Install Log has been implemented. The log resides on the client (requester) machine, and tracks whether packages from various servers have been retrieved and installed.

  • RSF automatically flags a package as "retrieved" when it is downloaded. A user-written installation program can then flag the package as "installed" using the new Log RSF Install (LOGRSFINL) command.

  • Pre-requisite and co-requisite checking is now supported. User-written installation programs can now use the Retrieve Package Install Info (RSFRSFINL) command to determine whether pre-requisite packages have been installed, and take appropriate action if they have not.

  • The Work With RSF Catalog display has been enhanced to support the new install log. The display now shows which packages have been retrieved or installed, and the list can be filtered by package status, allowing the user to display only uninstalled packages, installed packages, etc.

  • The Install RSF Package (INLRSFPKG) command has been enchanced to work with the new install log, further simplifying package installation. Plus the INLRSFPKG command can now be accessed by keying option "10" beside a package on the Work With RSF Catalog display.

  • The Retrieve RSF Package (RTVRSFPKG) command has been enchanced to check a package's install status before retrieving it, thus preventing an installed package from being accidentally retrieved again.

• Simplified TCP/IP Setup.  You can now specify either a friendly system name or an IP address for the "Remote System" parameter on the Add/Change Server directory entry commands. Previously, if you wanted to specify an IP address, you had to specify *INTNETADR for "Remote System" and then specify the IP address in a different parameter.

Release 6.0

↑

• TCP/IP Support.  RSF now supports native TCP/IP connections. Any TCP/IP connection is valid, including the Internet. 
  
  Files, objects and spooled files transmitted over TCP/IP connections can be automatically encrypted during transmission. Several levels of encryption are supported, including industry standard Secure Sockets Layer (SSL). 
  
  Changes have been made to the Add/Change Server Directory Entry commands to allow you to tie a given server to a TCP/IP address. All other RSF functions work just as they did in the previous release, without regard to whether the server being contacted is connected via dial-up link, LAN connection, or the Internet.

• Copy/Split Spooled Files.  A new command to allow you to make copies of spooled files and split spooled files into multiple parts for more effecient 
  printing has been added to library RSFTOOLS.  See command  CPYSPLFRSF.

• Use RSF to Send Spooled Files from the WRKSPLF Display.  A new command was added to library RSFTOOLS to allow you to key 1=Send beside spooled files on the WRKSPLF display to send the spooled files to another system using RSF. See command WRKSPLFRSF.

• Improved Line Selection.  With each release of RSF, the algorithm used to select/share available switched lines for dial-out is improved. This release is no exception. Now RSF selects available dial lines more efficiently.

• Schedule Transmission Function More Robust.  Changes were made to the Schedule RSF Transmission function to insure that all transmissions to a list of locations have the best chance of succeeding.

• New Optimization Option When Sending File Members.  A new optimization option on the Copy File Using RSF (CPYFRSF) command lets you compress large files or members before they are copied to the other machine.

Release 5.1

↑

• Remote Console Support.  RSF now provides remote console support, allowing you to monitor message queues on any number of remote AS/400s from a central machine. The new Start Message Queue Monitor (STRRSFMSGM) command lets you link message queues, such that messages received on the source queue are automatically forwarded to the target queue. When you answer a forwarded inquiry message, the reply is automatically sent to the source queue. Messages can be monitored by having each remote site automatically send them to the central site, or by having the central site poll each remote site. Messages can be filtered by severity and by generic message id to reduce the number of forwarded messages.

• New Commands Allow for Inter-machine Task Synchronization.  Several new RSF commands help you coordinate interdependent tasks running on multiple AS/400s. The Log Event (LOGEVTRSF) command lets you log a user-defined event to a log file locally or remotely. The Wait For Event (WAITEVTRSF) command lets you schedule a task to begin after one or more event conditions have been met. The Retrieve Event Attributes (RTVEVTRSF) command lets you query the status of a user-defined event. With these new tools, it's now easy to schedule a job to run on machine "A" only after certain tasks have been completed on machines "B", "C" and "D".

• User-Defined Options Supported.  User-defined options can now be keyed on the RSF WRKxxx displays, making these lists even more powerful. You define new options using option 9 on the PDM menu (STRPDM). User-defined options can contain substitution variables which are replaced at execution time. RSF supports a wide range of substitution variables. For complete details, see the on-line help text for the "Opt" field on the Work With Servers display.

• Filtering Parameters Provided on WRKxxx Commands.  New parameters on the Work With Servers (WRKRSFSRV), Work With Packages (WRKRSFPKG) and Work With Requesters (WRKRSFRQS) commands allow you to select which list items are displayed or printed. List items can be filtered by generic name and by text.

• Windows Graphical Interface Now Included With Base Product.  RSF Express, the graphical interface for RSF, is now included with the base product at no additional charge. RSF Express runs under Windows 3.x or Windows 9x on a PC attached to your AS/400. With RSF Express, you can move objects and spooled files between AS/400s by dragging and dropping with a mouse.

• Work With Catalog Display More Efficient.  With this release, when you use the Work With Catalog display to retrieve multiple packages from a remote server over a switched connection, the phone connection remains active until the last package is retrieved. In the past, RSF would hang up and redial 
  for each package. 
  
  Note, however, that individual server machines can still override this feature and force requesters contacting their machine to hang up after each individual request or after a certain time interval. See the help text for the HANGUP parameter on the Change Requester Directory Entry (CHGRSFRDE) command for more information about how this feature is controlled on the server machine.

• Canceled Requests End More Gracefully.  In the past, canceling an RSF request (i.e. using "System Request option 2") would end the request immediately but would not allow RSF to clean up outstanding object locks and table entries. This would sometimes cause problems for other users on the same machine who were initiating RSF requests. Other users might have gotten the "All lines in use.." message, or another message indicating a required object could not be allocated. 
  
  Now, any RSF request that ends abnormally--even those ended by "System Request option 2"--will still clean up all internal RSF tables and locks before the request ends. Whereas in the past, users were discouraged from canceling RSF requests with "System Request 2", this practice is now fully supported.

• Send/Retrieve Objects Even While They're In Use.  A new "Save While Active" parameter on the RSFTOOLS commands for sending and retrieving libraries, objects and documents allows you to transmit items even if they're currently being used.

• Active Connection Count on Work With Servers Display.  The Work With Servers display now shows the number of requests that are currently active for each server. If, for example two users were passed through to server ABC and a batch job was retrieving a package from the same server, the number 3 would show in the Active Connections column of the display next to server ABC.

• Log Display Enhanced.   The display presented when using the Work With RSF Log (WRKRSFLOG) command has been enhanced. Two additional options can be specified for a log entry. Keying "8" beside a log entry Enter displays the text of the associated error message, if any. Keying "12" beside a log entry displays the Work With Job panel for the AS/400 job associated with the log entry.

• Pass-Through User Profile.  You may now specify a remote user profile and password on the Start Pass-through Using RSF (STRPASRSF) command to bypass the Sign-on display when passing through to a remote system. The QRMTSIGN system value on the remote system must be set appropriately or your request to bypass the Sign-on screen will be rejected.

• Special Access Rights For *CURRENT Users.  Since the first release of RSF, you could use the Requester Directory to regulate the rights and restrictions that apply to remote requesters accessing your machine. Each entry in the Requester Directory specifies the rights for a particular remote machine serial number. 
  
  Now you can specify a different set of access rights for a remote machine when the job initiating the request on the remote machine is a target RSF pass-through job that was started on your own machine. 
  
  This new feature would allow you, for example, to retrieve objects from your machine while passed-through to a remote machine, and still prevent users signed directly on to the same remote machine from retrieving objects from your machine.

• New *REQUESTER Special Value for Remote User Profile.  When you're entering commands in a target RSF pass through session or in other types of RSF server jobs, you can now specify *REQUESTER for the User Profile parameter with RSFLINK and on the Copy File Using RSF (CPYFRSF) command. This new value--which is only valid if *CURRENT is specified for Server id--connects back to the original system using the same user profile that was used to initiate the original RSF connection. 
  
  For example: USER1 on SYSTEMA uses the STRPASRSF command to connect to SYSTEMB. User profile USER2 is used to sign on to SYSTEMB. Now the following command, executed in the target pass-through job on SYSTEMB, will copy files from SYSTEMA to SYSTEMB and will have USER1's authority to the objects on SYSTEMA:

 CPYFRSF ACTION(*RTV) FROMFILE(MYLIB/QCLSRC) SERVER(*CURRENT) FROMMBR(A*) USER(*REQUESTER)

• Package Transmission Time Displayed.  In addition to "Percent Complete" information, elapsed time and time remaining are now shown when sending/retrieving packages, objects, libraries, documents and folders.

• Better Text on Line, Controller and Device descriptions.  RSF now uses the text on line, controller and device descriptions that it creates to indicate which server location the configuration objects connect to.

• Preprocessing Program Capabilities Enhanced.  Preprocessing programs can now override the save file and cover letter file associated with an RSF package at execution time.