FOCUS Facilities Under TSO

In this section:

FOCUS facilities under TSO include:


Top of page

x
Using FIDEL

The actual terminal control program is loaded dynamically, according to the program name you specify in the DATA VIA subcommand of MODIFY.

DATA VIA FIDEL
END

A DATA statement is not required in a MODIFY which uses CRTFORM if the procedure will be executed on a 3270-type terminal. FOCUS automatically loads FIDEL if the MODIFY procedure uses CRTFORM.


Top of page

x
TED Editor

How to:

You can edit a file with TED using the TED command. You can also edit a file with your system editor using the IEDIT facility. For information about IEDIT, see Invoking Your System Editor With IEDIT.



x
Syntax: How to Enter TED
TED ddname

or

TED 'prefix.qualifier1.qualifier2...(member)' 

or

TED name

where:

prefix

Is a prefix other than the one you are working under. If you are working within your own prefix, you do not have to specify the prefix or the single quotation marks around the data set name.

qualifier

Is the name of the file within the prefix. Qualifiers are separated with periods. You can have up to 44 characters in a data set name.

(member)

Is necessary only when you are using a partitioned data set. For sequential data sets, a member name (enclosed in parentheses) is not used.

name

Is either the ddname of an allocated sequential data set or the member of a partitioned data set allocated to the ddname FOCEXEC. Specify only from the FOCUS command line.

FOCUS searches for the ddname of a sequential data set first. If a sequential file does not exist, FOCUS continues and searches for the member of a partitioned data set allocated to the ddname FOCEXEC. To change the search order and force FOCUS to search for the member first, issue:

TED FOCEXEC(member)


Example: Entering TED

You can specify a valid data set name or ddname with a member name if the file is a PDS. Note the following examples:

TED

Edits the last executed FOCEXEC.

TED TEST

Edits the data set allocated to ddname TEST or the member name in a partitioned data set allocated to the ddname FOCEXEC.

TED FOCEXEC(A)

Edits member A of the data set allocated to ddname FOCEXEC.

TED X.DATA(REPT)

Edits member REPT of the data set prefix.X.DATA.

TED 'USER1.X.DATA'

Edits the data set USER1.X.DATA.



x
Syntax: How to Issue TSO Commands From TED
{TSO|MVS} command

where:

MVS|TSO

Specifies the operating system. The MVS prefix may be substituted for the TSO prefix.

command

Is a TSO command

Note:



x
Syntax: How to Submit a Job From TED

You can submit a job from TED by using the following syntax to submit the current file to z/OS:

SUBmit 


Example: Creating a TED Profile

On entry to TED, a search is made for a profile as member TEDPROF of the data set allocated to ddname FOCEXEC. If found, it is processed by TED before the first screen appears. The profile may issue most TED commands that do not involve any file manipulation (for instance such commands as SPV and FILE may not be issued in the profile). The most common use for a profile is to establish a prefix area and perhaps a scale and PF key assignments. A typical profile might be:

1. NUM ON 
2. SCALE ON 
3. PF 6 FILE

where:

  1. Sets the prefix area on and displays line numbers.
  2. Displays a scale on line 2 of the screen.
  3. Redefines the PF6 key as FILE.

Top of page

x
GRAPH

Reference:

FOCUS uses the IBM program product Graphical Data Display Manager (GDDM) to create graphics on IBM high resolution devices (see list in the IBM GDDM Guide for Users).

A GDDM stub must be linked into FOCUS before GDDM graphics may be used. This must be performed once as part of the FOCUS installation procedure. See the z/OS Installation Guide.

To run color graphics on IBM 3270-type terminals, the GDDM load library must be allocated to ddname STEPLIB in your logon procedure.

You can use GDDM facilities for saving deferred graphic output. Before saving graphs, you must allocate ddname ADMSAVE as the PDS that will receive your graph(s). This can be allocated from within FOCUS as follows:

ATTRIB DCBG LRECL(400) RECFM(F) BLKSIZE(400)
ALLOC F(ADMSAVE) DA(ADMSAVE.DATA) DIR(5) SP(10 2) -
TRACKS USING(DCBG)

After creating the graph to be saved on your screen, press PF1 to save it. A prompt appears asking for the name of the "save" file. Enter a name and press the Enter key. The screen is saved in the ADMSAVE PDS as the member you have named. Thus saved, the file can be retrieved by compiling and linking the GDDM program ADMUSF2 (see the IBM GDDM Guide for Users).

Use the IBM-supplied utility ADMOPUV to print GDDM graphs on the IBM 3287 printer. ADMOPUV is run using the file and address of the printer as parameters (see the IBM GDDM Guide for Users for more information).

To get GDDM printouts from FOCUS GRAPH:

  1. Generate a graph.
  2. To get a printout, press PF4. Respond to the resulting prompt with the local printer name. The graph will be routed to the printer right away if the background print utility job (ADMOPUT) is active. If it is not active, you have to repeat the procedure with the PF4 key when the background job is running.

The ADMOPUV utility supplied with GDDM must be running in the background to take the printer output from GDDM to a local printer. Details about this utility can be found in the IBM GDDM Guide for Users.

It takes from five to fifteen minutes to print a graph depending on its complexity and colors. Keep in mind that the screen has six colors while the printer has only four, so colors (except for red, blue, or green) appear as black.



x
Reference: Allocating Files to Hold Formatted Graphic Output

When allocating your own file for storing non-GDDM deferred graphic output, specify only the data set name and the DISP parameter. Do not specify the DCB parameters. FOCUS specifies them when it writes the file.

If you let FOCUS allocate the SAVE file, you must copy it if you want it to remain after the end of the FOCUS session.

You can send the output of many GRAPH commands to one graphics SAVE file by setting DISP=MOD. If you do, however, make sure that all of the deferred graphic output is headed for the same graphic device.



x
Reference: Using the ICU Interface

You can use FOCUS to generate graphs in conjunction with IBM's Interactive Chart Utility (ICU is a component of PGF). Specify normal FOCUS GRAPH syntax to use any of its features. The ICU Interface can either place the user directly in the ICU environment or can save the graph format and data for subsequent ICU processing. To use the ICU Interface, issue the command:

SET DEVICE=ICU

See the FOCUS ICU Interface User's Manual for more information.


Top of page

x
Accessing the FOCUS Menu

How to:

The FOCUS Menu is a convenient way to access FOCUS facilities using windows. It enables you to navigate through menu options, selecting FOCUS features such as the Talk Technologies, DEFINE, JOIN, and query functions.

For successful execution, the following minimal allocations are necessary:

DYNAM ALLOC FILE FOCEXEC DA prefix.FOCEXEC.DATA SHR REUSE
DYNAM ALLOC FILE ERRORS  DA prefix.ERRORS.DATA  SHR REUSE
DYNAM ALLOC FILE FMU     DA prefix.FMU.DATA     SHR REUSE

where prefix is the high-level qualifier selected for FOCUS installation at your site. Any other data sets may be concatenated to these ddnames.



x
Syntax: How to Access the FOCUS Menu

Issue the command

EX FMMAIN

or

Invoke the FOCUS menu automatically when you enter FOCUS by editing the member SHELPROF in the FOCEXEC.DATA partitioned data set (provided on the installation tape). Remove the comment characters from the line with the -INCLUDE command. The lines should appear as follows:

-* This FOCEXEC will be executed only after PROFILE focexec execution
-* has been completed.
-INCLUDE FMMAIN

Top of page

x
Accessing the FOCUS ToolKit

How to:

The FOCUS ToolKit is a menu-driven tool that walks the end user through many FOCUS facilities. Topics listed on the ToolKit menu include: reporting facilities, maintain data, decision support, and dictionary maintenance. The ToolKit option supports FOCUS and operating system utilities, as well as access to SQL facilities. An online guide to using the system is also included. The ToolKit option may be customized to provide specific site information, user selections for print destination, and data access.

For successful execution, the following minimal allocations are necessary:

DYNAM ALLOC FILE FOCEXEC  DA prefix.FOCEXEC.DATA  SHR REUSE
DYNAM ALLOC FILE ERRORS   DA prefix.ERRORS.DATA   SHR REUSE
DYNAM ALLOC FILE FMU      DA prefix.FMU.DATA      SHR REUSE
DYNAM ALLOC FILE ISHFALOC DA prefix.ISHFALOC.DATA SHR REUSE

where prefix is the high-level qualifier selected for FOCUS installation at your site. Any other data sets may be concatenated to these ddnames. The members ISHFPROF (the background window) and ISHDPNTR (printer selection list) must be available in ddname ISHFALOC when you execute the ToolKit. These files are created with the installation FOCEXEC ISHFINSTL. The printer list may be updated using the FOCEXEC ISHFPNTR.

The ToolKit dynamically accesses files that are identified to the ToolKit. This is accomplished by creating a FOCEXEC that performs the necessary allocations and USE statements for a given file. This FOCEXEC is stored in the data set allocated to ddname ISHFALOC with a member name that corresponds with the file name (as used by FOCUS).



x
Syntax: How to Access the FOCUS ToolKit

Issue the command

EX ISHFSHLL

or

invoke the FOCUS ToolKit automatically when the user enters FOCUS by editing the file SHELPROF FOCEXEC, which is found on either the FOCUS production disk or on any accessed disk, to read:

EX ISHFSHLL
-EXIT


Example: Dynamically Accessing Files Identified to the Toolkit

For example, the member CAR accesses the CAR FOCUS data source:

DYNAM ALLOC FILE CAR DA prefix.CAR.FOCUS SHR REUSE 
-EXIT

Top of page

x
Accessing Power Reporter

How to:

Power Reporter is a user-friendly full screen front end to the FOCUS Report Writer. Designed for both end users and application developers, it features pull down menus that enable users to create FOCUS report requests in non-linear order, preview the report format and generated code, and much more. Power Reporter includes capability to create DEFINEs and JOINs, save requests for later revision, and display information about the FOCUS session.

For successful execution, the following minimal allocations are necessary:

DYNAM ALLOC FILE FOCEXEC DA prefix.FOCEXEC.DATA SHR REUSE 
DYNAM ALLOC FILE ERRORS  DA prefix.ERRORS.DATA  SHR REUSE 
DYNAM ALLOC FILE FMU     DA prefix.FMU.DATA     SHR REUSE 

where prefix is the high-level qualifier selected for FOCUS installation at your site. Any other data sets may be concatenated to these ddnames.



x
Syntax: How to Access Power Reporter

Issue the command:

EX PWREP

Top of page

x
National Language Support

How to:

FOCUS is designed with consideration for National Language Support (NLS). FOCUS stores data as entered and retrieves the data based on the current code page mapping. FOCUS can be configured for local language messages and keyboards. For installation instructions, refer to the z/OS Installation Guide. Your Information Builders' representative can provide a list of available language choices.

The ? LANG command can be used to determine the current language setting and parameters pertaining to language, such as continental decimal notation.



x
Syntax: How to Determine Current Language Settings
? LANG

FOCUS supports languages that require two bytes of storage per character, such as Kanji. For more information, see the Describing Data manual.


Information Builders