Re: need help with this rpg application

[Booth Martin <booth@xxxxxxxxxxxx>]

If I am understanding the process, I might consider something like this:
1-It sounds like what is needed initially is read-only on a whole bunch 
of files.  Separate sandbox files sounds to me like an unnecessary 
complication.
2-Would dataqueues work here?  Create your dataqueue entries through the 
initial process and then have the final process fed by the dataqueue?
3-If this new process is going to become all that complex and 
significant an investment of time and energy then is it time to bite the 
bullet and go one more step and get the application totally off of a 
5250 session?

On 7/16/2012 1:52 PM, Dave wrote:
> Imagine an application for entering client information to create
> transactions. Users have been granted their wish to create
> transactions with very little controls by using a "sandbox". Basically
> they've been given a library containing copies of all the necessary
> production files. That way they can create as much as they like with
> the information they have as soon as it becomes available. Now for the
> hard part: If the transaction is accepted, the user needs to be able
> to select it in a subfile, which will then take them to the normal
> creation application I mentioned at the start. At this point, the
> library list will have changed to the normal production environment,
> so that the sandbox files are no longer on line. The application will
> display several screens before finalising the transaction. Each screen
> needs to be populated with the information available in the sandbox,
> the user completing the missing information. The idea is that the user
> will not have to retype all the information on all the screens.
>
> It has been suggested to call the application in a separate activation
> group after having copied the sandbox information to the production
> files. In case of abandoning the transaction, the application already
> knows how to delete the information from the database.
>
> Copying the uncontrolled sandbox data to the production files just
> doesn't seem right to me, even if it can be successfully deleted and
> even though the user will have to correct any incorrect data. Has
> anyone another idea how this might be achieved? What about a special
> file containing all the information from the sandbox files? Is that
> possible?