Flynet Simulated Host

Map Tag

Map Tag

Previous topic Next topic  

Map Tag

Previous topic Next topic  

The Map Tag is used to provide the screen's layout in a simple, direct fashion.  A key tip in the creation of Simulated Host custom scripts is to copy screen maps from the Flynet Viewer Trace Viewer application, where they are displayed in the same format used by the expected map contents.

 

The Map Tag should be immediately followed by the <![CDATA[ opening tag so that the special characters and carriage returns found in the map are not altered by the MSXML parser used in the Simulated Host.

 

The Map Tag's attributes are as follows:

 

Attribute

Default / Required

Description

name

"default"

Name of the map, with the name of "default" automatically loading the map should there not be an explicit load request in the onload Script event block.

type

"normal"

Allowed: normal or alternate

 

If normal then the "normal" rows and columns defined in the parent SimHost tag will be used.  If alternate than the alternate screen rows and columns are assumed.

formatted

"yes"

Allowed: yes or no

 

If yes then the screen is assumed to be formatted and will contain attribute bytes.  If no then the screen is "unformatted", which is common in initial logon screens in 3270 systems.

framed

"no"

Allowed: yes or no

 

If yes then the map is assumed to be "framed" by numbers describing the column and row numbers, as displayed in the trace file viewer.  Use yes when you copy-and-paste from the trace file viewer to make the paste operation easier.

cursorRow

row of the first input field in the map

Use this to set the initial row that the cursor is on when the screen is displayed.  If omitted, the Simulated Host will locate the first input field defined and use its row.

cursorColumn

column of the first input field

See description of cursorRow...

numFields

empty / not defined

Enables defining which fields on the map are to be numeric only fields.  Format is:  r,c|r,c

 

Where r=row and c=column, separating field entries with the vertical bar.

 

Example, which defines 3 fields as numeric only:

 

numFields="4,33|5,33|15,2"

 

Child Tags Allowed:

 

 No child tags allowed--Map contents should be one <![CDATA[ text block

 

Map Contents

 

The text inside the CDATA block should be one line for each row of the screen (the number of rows depends on the type attribute and the row/column attributes defined in the SimHost tag.

 

When the framed attribute is "yes" then the text definition of the screen will be bounded with two rows of colum identifiers and two columns of row identifiers.  Generally, if you are not copying a map from the Flynet Viewer trace file, don't bother with frames unless you find them helpful in composing the screen.

 

The map contents, aside from the frame numbers is a direct map of the screen you will view in the Simulated Host application.  To support attributes, special characters are used.  These characters are as follows:

 

]        Plain, protected text, normal display

}        Plain, protected text, bold display

~        Protected text, hidden (can be read by a 3270 program but not visible to user)

[        Input field, normal display

{        Input field, bold display

^        Input field, hidden display (for password entry)

 


Example:

 

<Map framed="yes" type="normal" formatted="yes" cursorRow="6"

    cursorColumn="24"><![CDATA[

           1         2         3         4         5         6         7         8

  12345678901234567890123456789012345678901234567890123456789012345678901234567890

1 }CICS Signon

2

3

4  DFH3561A TYPE IN YOUR NAME AND OPTIONALLY PASSWORD

5

6           Name     ==>[                    }

7           Password ==>^        } (Demo)

8           Language ==>[ }

9                       }        }

10  }

11  }

12

13

14

15

16

17

18

19

20

21

22

23 }ENTER==> Process, CLEAR==> Reset, PF3==> Previous Screen

24

]]></Map>>