The three functions, EDTFIL, DSPFIL and SELRCD, have subfiles. For these functions, if the end user tries to continue scrolling past the end of the subfile, S (CA 2E) Distributed file I/O control causes an automatic connection to be made to the next RDB at the end of subfile for the RDB. Similarly, if the end user rolls beyond the top of the subfile, a connection will be made to the previous RDB. If a Rollup or Rolldown beyond the current extent is attempted, and the current RDB is the last (or first) in the configuration list, a message appears stating that there are "No more RDBs to connect to".
These automatic connections are subject to a confirm prompt if confirm prompting has been requested for the function. This confirm prompt appears with a message, "Confirm Connect to Next/Previous RDB," as a request to confirm the connection, not the changes. Any changes are lost if not previously confirmed by the end user.
End users can respond N to the confirm prompt to return without connecting, and press Enter to confirm any changes they may have made.
The subfile functions, EDTTRN and DSPTRN, do not have the roll functionality. This is because they have an inherent key screen concept similar to the EDTRCD and DSPRCD functions. Further, an EDTTRN function has infinite roll forwards, as you can add records at the end of an EDTTRN function. A DSPTRN function, while having a defined roll boundary, currently has rolling controlled by i OS, because the whole subfile is built before it is displayed.
Note: All functions with panels, including EDTTRN and DSPTRN, have the F22-Change RDB function under CA 2E Distributed file I/O control.
|
Copyright © 2014 CA.
All rights reserved.
|
|