Branching procedures

Subject: Branching procedures
From: dan roberts <droberts63 -at- earthlink -dot- net>
To: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 23 Feb 2000 10:27:55 -0500 (EST)

I'm stuck, and I can't figure a good way out.

I'm doc'ing mainframe (ISPF) procedures that can include a number of runtime options. The user specifies input data sets and runtime options on the initial screen. Depending on the runtime options the user selects, various other screens might appear, one per option.

For example, a typical flow is:
1. Component screen, for input data sets and options (filter statements, report titles, report parameters)
2. Possible screen for filters.
3. Possible screen for report titles.
4. Possible screen for report parameters.
5. Back to the regular flow, for print options, job cards, jcl review, and submitting the job.

At first, I'd want to break out each of these possibilities into a subsection. But each of these possibilities is a stage in the process, a means to an end, not an end inandofthemselves (although that might be the best way to go).

But if I keep to one procedure flow, I get all these "if" conditions: "If you selected option X way back 12 screens ago, then this panel displays now. Otherwise the next panel appears, unless you didn't select option Y way back 12 screens ago..."
You get the idea. It's just nasty.

If anyone can help me out with other ways to tackle this problem, I'd appreciate it. If you can, please CC droberts -at- isogon -dot- com so that I can get your responses. Thanks!

droberts -at- isogon -dot- com

Previous by Author: Re: Problems Documenting An Application
Next by Author: Word styles in HTML
Previous by Thread: Re: W97 embedded fonts - getting to work
Next by Thread: Re: Branching procedures

What this post helpful? Share it with friends and colleagues:

Sponsored Ads

Sponsored Ads