This adapter is used to run tests on the 5250 Adapter. This adapter allows us on the one hand to run tests on AS/400 mainframe screens and also to generate macros that allow us to automate tests on “transformed to HTML” systems.

In the initialization process it is necessary to supply the information to connect to the As400 5250 server. That is the information of the Adapter object.

This executor must be downloaded:

5250 - We are going to fill in the necessary parameters of the adapter.

Adapter = 5250
Session Name = Name that we want to give.

Host:
- VPS = PUB400.COM
- TAST1 = descfvkr.de.scf.corp

Port:
- VPS = 23
- TAST1 = 23

Proxy Port
- 1080 for the 2 environments.

tnEnhanced
- Marked for the 2 environments.

Screen Size
- 24 * 80 for the 2 environments.

SSL
- NONE For the 2 environments.

Codepage
- INTERNAL - Built-in EBCDIC conversion (CP037).
For the 2 environments.

• containsText(Text): This function evaluates whether within the host screen, there is a specific text that we define in said function.
  1.- In the message mapping, the text that we want to find is added in the Value field.

• nextScreen: This function directly advances to the next navigation screen previously you will have had to go through it to find it).
  It does not require parameters in the encoding. (Function not activate at the moment).

• previusScreen: This function directly advances to the previus navigation screen.
  It does not require parameters in the encoding. (Function not activate at the moment).

• readField(Field,Offset,Length): This function reads a field that we define in its parameters:
  
  • Parameter = Field→ Position (numeric) in which the field is located. it is counted visually on the screen, as it is not indicated anywhere.
    
  • Parameter = Offset→ Position 0.
    
  • Parameter = Length→ Length of the field that we are going to read.

• readRow(Row): This function reads a certain line from the screen. The whole line.
  
  • Parameter = Row> Position (numeric) where the line is located.
    
    This data can be seen at the bottom right of the screen:
    
    
    

• readScreen: This function reads the screen you are positioned on.
  Function without parameters.

• rowContaintsText(Text,Row): This function checks if there is a certain text in a screen free.
  
  • Parameter = Text → We introduce the text to search.
    
  • Parameter = Row→ Position (numeric) of the line.
    
    This data can be seen at the bottom right of the screen.
    
    
    

• waitForCursor: This function waits for the cursor to appear on the screen that we want to see next.
  
  • Parameter = timeinSeconds → Value: Time in seconds.
    

• writeAftherLabel (Label, Text): This function writes any text to the screen, after the label that we have defined in the Label parameter has been shown (on the screen).
  
  • Parameter→ Label = Value→ Text to appear.
    
  • Parameter→ Text = Text that we are going to write.
    

• writeBeforeLabel (Label, Text): This function writes any text to the screen before the label that we have defined in the Label parameter has been shown (on the screen).
  
  • Parameter→ Label = Value→ Text to appear.
    
  • Parameter→ Text = Text that we are going to write.
    

• writeField (Text, Field, Offset): This function writes in a certain field the value that we define in the Text parameter.
  
  • Parameter→ Text = Value→ Text that should appear.
    
  • Parameter→ Field = Field that we are going to write.
    
  • Parameter→ Offset = Field position (Position 0).

• writeKey (Key): This function executes a predefined key on the screen.
  (ENTER, PF8, PF4… ..etc).
  
• Parameter→ Key = Value→ Function key.
  

• writeText (Text, Row, Column): This function writes a text in a defined position.
  (line and column).
  
  • Parameter→ Text = Value→ Text to write.
    
  • Parameter→ Row = Value→ Line Number.
    
  • Parameter→ Column = Value→ Column number.
    
    This data can be seen at the bottom right of the screen.
    
    
    

As already mentioned in the Introduction, with this adapter you can generate macros that allow you to automate tests in “transformed to HTML” systems. We are going to explain how to record a series of keyboard actions and then execute them.

We connect to the emulator:

Right-click to access the Recording Macro and the Record tab.

We name the file to be recorded and accept. The recording will start.

When we finish and end the recording, we will access again with the right button to the Recording Macro and to the Finish Recording tab.

The file, once the test recording is finished, is saved to: C:\Users\xxxxx\OneDrive\Documentos\5250 where xxxxx will vary depending on the name of each user. Later we will need to find this file to import it.

Next, we access the TAST tool.

• Check the new diagram box and go to Domain, Project, Folder, Diagram name and Diagram description, as we always do when we design a new diagram. Then the Canvas or blank canvas appears.
• Access the toolbar and click on the Assistants box.
• A drop-down menu with different options will appear. The options to choose are:
  - Import from 5250 to 5250.
  - Import from 5250 to HTML.
  
• We import from Assistants the file that we have recorded and saved in the C: Drive.
  
• In either of the two options provided by the Assistants box, a diagram will be automatically generated, which will reflect step by step, the whole recording process of the different actions performed and in which two adapters will appear, the User Object adapter and the 5250 adapter.
• Save and validate the diagram.
• And finally, we will take it to the TAST client to execute it.