TAST DokuWiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Host Adaptor 3270 ======



===== Introduction =====

This adapter is used to run tests on the 3270 Host Adapter. This adapter allows us on the one hand to run tests on HOST mainframe screens and also to generate macros that allow us to automate tests on "transformed to HTML" systems.
===== Configuration =====

In the initialization process, it is necessary to supply the information to connect to the Host 3270 server. That is the information of the Adapter object.


===== Initialization Parameters =====

====Connection====

  * **Host:** Name of the machine or IP address. Required. SESSION_HOST.
  * **Port:** Connection port. Required. SESSION_HOST_POST. It is 23 by default. 
  * **Use proxy:** Check this if you want to use a proxy.
  * **Proxy host:** Name of the proxy or IP address. It is localhost by default.
  * **Proxy port:** Port of the proxy. It is 1080 by default.
  * **LU_Name:** Name of the connection LU, optional.  
  * **Enhanced:** Indicates whether the Enhanced protocol is used. (by default is not checked). SESSION_TN_ENHANCED. 
  * **Telnet_Negotiated:** The telnet information. 
  * **Server_Authentication:** Information of authentication to the 3270 Server. 
  * **Client_Certificate_Autentication:** Certificate for Authentication.
  * **Personal_Certificate:** Personal certificate for Authentication.
  * **Personal_Certificate_File Path:** Path to the Certificate for Authentication.
  * **Personal_Certificate_pass:** Pass to the Certificate for Authentication.
  * **Certificate_Name:** Name of the Certificate.
  * **Certificate_Pass:** Pass to the Certificate.
  * **Certificate_Source:** Source to the Certificate.
  * **Certificate_URL:** Url to Certificate.
  * **Prompt_Required:** PromptRequired.
  * **Certificate_Based_Keys:** Certificate Based Keys.
  * **SSL:** SSL. 
  * **KeyStore_FilePath:** KeyStore File Path. 
  * **P12_FilePath:** P12 File Path. 
  * **KeyStore_Pass:** KeyStore Pass. 
  * **Certificate_Trusted:** Certificate for Authentication.
  * **Code_Page:** Code Page. By default it is INTERNAL – Built-in EBCDIC conversion (CP037). 
  * **Session_Type:** Session Type.
  * **Security_Type:** Security Type.
  * **Protocol:** Protocol.
  * **Protocol_Version:** Protocol Version.
  * **Certificate_Type:** Certificate Type.\\ \\ **3270 Adapter Connection to execute diagrams in Tast**\\ \\ 3270 – We are going to fill in the necessary parameters of the adapter.\\ \\ **Adapter =** 3270\\ **Session Name =** Name that we want to give.\\ **Host:**\\ - VPS = 127.0.0.1\\ - TAST1 = vipadpre.scger.pre.corp\\ **Port:**\\ - VPS = 3270\\ - TAST1 = 23\\ **TN3270E =** For the 2 environments marked. It is checked by default.\\ 


===== Predefined Functions =====



  * **clearAndWriteField**: Clears and writes a text in a field in the indicated field. 
    * Parameter Field: Field number starting with 1 
    * Parameter Offset: Offset in the field starting with 1   
    * Parameter Value: Text.

  * **clearField**: Clears the field with field number entered in the parameter.

  * **containsText(Text):**This function evaluates if within a host screen, there is a specific text that we define in this function.\\  
      *Parameter Text: In the message mapping, the text that we want to find is added in the "Value field".

  * **getLenghField**: Gets the length of the field with field number entered in the parameter.

  * **nextScreen:** This function advances directly to the next navigation screen (you will have previously had to go through it to find it). It requires no parameters in its coding.

  * **previusScreen:** This function advances directly to the previous navigation screen. No coding parameters are required.

  * **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.
     *Parameter Offset: Position within the field from which you want to read.
     *Parameter Length: Length of the field to be read.\\ These 3 parameters are obtained by clicking the right mouse button, on the field we want to read.\\ 
{{ :en:image_2021_01_11t12_08_14_736z.png?400 |}}\\  

  * **readRow(Row):** This function reads a particular line on the screen. The whole line.\\
     *Parameter Row: Position (numerical) in which the line is located.\\ This parameter is obtained by clicking the right mouse button on the line we want to read.\\  
{{ :en:image_2021_01_11t12_08_14_736z.png?400 |}}\\  

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

  * **readScreenByRows**: Reads the current screen by rows. 

  * **rowContaintsText(Text,Row):** This function checks if a certain text exists in a screen line.\\
        *Parameter Text: Enter the text to search for.
        *Parameter Row: Position (numeric) of the line.\\ These parameters are obtained by pressing the right mouse button, on the line we want to find the defined text.\\ 
{{ :en:image_2021_01_11t12_08_14_736z.png?400 |}}\\  

  * **waitCRC(screen_CRC):** This function waits for the screen we want to see next.\\ 
        *Parameter screen_CRC: Value -> Obtained by right-clicking on the screen we want to display.\\ 
{{ :en:image_2021_01_11t12_08_14_736z.png?400 |}}\\  

  * **waitFor**: Wait for the time in seconds received in the parameter to elapse.

  * **waitForChange(TimeOut(msec)):** This function waits for time for the next screen to be displayed.
        *Parameter TimeOut (msec): Value -> Time in msec to wait to be displayed.

  * **waitForText(Text,Row,Column):** This function waits for a certain text to appear before displaying the following screen.\\ 
       *Parameter Text: Value-> Text to be displayed.
       *Parameter Row: Row of the word.
       *Parameter Column: Column of the word.

  * **writeAftherLabel (Label,Text):** This function writes to the screen any text, after the label we have defined in the Label parameter has been displayed (on the screen).\\ 
       *Parameter Label: Value-> Text to be displayed.
       *Parameter Text: Text that we are going to write.

  * **writeBeforeLabel (Label,Text):** This function writes to the screen any text, before the label we have defined in the Label parameter has been displayed (on the screen).\\ 
       *Parameter Label: Value-> Text to be displayed.
       *Parameter Text: Text that we are going to write.

  * **writeField (Text,Field,Offset):** This function writes to a given field the value we defined in the Text parameter.\\
       *Parameter Text: Value-> Text to appear.
       *Parameter Field: Field to be written.
       *Parameter Offset: Position of the field.\\ These parameters are obtained  by right-clicking on the screen we want to display.\\ 
{{ :en:image_2021_01_11t12_08_14_736z.png?400 |}}\\ 

  * **writeKey (Key):** This function executes a predefined key on the screen.\\ (ENTER, PF8, PF4, etc…).
       *Parameter Key: Value-> Function key.

  * **writeKeyUntilFind(Key, Text)**: This function executes the function key (Key) and waits for the text (Text) to appear on the screen.

  * **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-> Row Number.
        *Parameter Column: Value-> Column number.\\ These parameters are obtained by right-clicking on the screen we want to display.\\ 
{{ :en:image_2021_01_11t12_08_14_736z.png?400 |}}\\ \\ 


===== Macro generation=====

As already mentioned in the Introduction, with this adapter, it is possible to generate macros that allow to automate tests in systems "transformed to HTML". We are going to explain how to record a series of keyboard actions, in order to execute them later.\\ \\  We connect to the 3270 emulator:  

{{ :1emulador3270.png?&400 |}}\\ 

Click on the Macro option to record the test and then check the Record option in the drop-down menu that appears.\\ 

{{ :2emulador3270.png?&400 |}}\\ 

Give a file name.\\ 

{{ :31emulador3270.png?&400 |}}\\ 

And we start recording, confirming by clicking the OK checkbox.\\ 


{{ :4emulador3270.png?&400 |}}\\ 


Once we finish, we stop recording by clicking Stop recording in the drop-down menu.\\ 

{{ :5emulador3270.png?&400 |}}\\ 

And confirm the stop by clicking on the OK checkbox.\\
 
{{ :6emulador3270.png?&400 |}}\\  

This process generates a **toExport** file that is automatically saved in the following path:\\ **C:\Users\xxxxx\jagacy_data**\\  where **xxxxx** will vary depending on the name of each user. Later we will need to find this file to import it.\\  



Next, access the TAST tool.
  * We check the new diagram box and access 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 3270 to 3270.\\   - Import from 3270 to HTML.\\ 
  * We import from the wizard the **toExport** file that we have recorded and saved in the **C:** Drive.\\
  *  In any 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 3270 adapter. 
  * Save and validate the diagram.
  * And finally, we will take it to the TAST client to execute it.
TAST DokuWiki

User Tools

Site Tools

Page Tools
