SNA Conformance Testing [using SDTF]
How and Where to Start?

The following steps will aid in trouble-free operation of SDTF:

• Choose the machine upon which SDTF will be installed based on desired performance criteria (i.e. faster machines will provide better stresses). A complete SDTF system requires at least 40 Mbytes of free disk space. An additional 30 Mbytes of free space is recommended to allow capturing large trace/log files.

• Follow the Installation Quikstart information included with SDTF and install the software on the selected PC.

• Review the SDTF default configuration parameters ('Options' on the main menu) for suitability with your intended testing implementation/client. Although the SDTF default parameters will allow the system to start, the following parameters should be reviewed for suitability with the Implementation Under Test's (IUT) configuration:
  • SDLC systems - SDLC station address, NRZ or NRZI;
  • LAN systems - the Workstation MAC address (SDTF.SYN file); and
  • All systems - the SNA DAF parameter.
  
  
  Note: Changing the LAN Workstation address involves editing the "SDTF.SYN" file which contains the list of valid MAC addresses and IUT synonym names.
  
  
  Refer to Chapter 4 of the SDTF User Reference Manual for details on the configuration and operation of SDTF.

• Physically attach the implementation to be tested using an RS-232 synchronous modem/modem eliminator and cable or LAN adapter cable. Start the IUT.

• Run a simple test to verify the connection to the IUT.
  • For a 3x74, 5250, or RJE system, change to the \sdtf7\sdtf3x74 subdirectory and run SDTF.EXE. Choose the library and test as follows:
    • IUT Library Test
      
    • 3x74 BARTS 099
      
    • 5250 LU7 001
      
    • RJE BARTSLU1 021

    and check for the correct results as shown in the appropriate User Reference Manual.

  • For an LU6.2 system, change to the \sdtf7\sdtflu62 subdirectory and run SDTF.EXE. Choose the TC62 library and run test 001. Verify these results with the LU6.2 Results Analysis Manual.

• Now choose from SDTF's extensive test libraries according to your testing objectives. The following table shows the relationships between testing objectives, SNA product types, and the SDTF test libraries.

  Testing Objectives	SNA Product Type
  	RJE	3x74	5250	LU6.2
  Data Link Control	DLC,DLCA	DLC,DLCA EFF74:1	DLC, DLCA	DLC,DLCA, DLCN, DLCS
  SNA Layers	PC,TC, SC,DFC	PC, TC, SC, DFC, EFF74:2-5,	EFF5250	PC62, TC62, 5C62, DFC62
  Management Services		SNAMS
  Secondary		SECOND
  Display	BARTSLU1	BARTS, LU2A, LU2B, LU2C, LU2D, LU2E, LU2F, LU2G	LU7	APPC3270
  Printer	SCSRJE	LU1, LU1A, LU1B, LU1C ,IPDS, LU1D, SCS, SCSC LU3, LU3A, LU3B, DSC	LU4
  Multi-PU		SNAA, LU2A, LU2C, LU2F
  Multi-LU		SNAA, LU2A, LU2B, LU2C, LU2F, LU2G	LU7A
  LU6.2 API				EFF62:Native Verbs & CPI-C using Basic & Mapped Conversations
  LU6.2 Functions				RM62, SM62, CO62
  SAA				LU62B
  APPN End Node				AENPRI, AENSEC, AENNEG, AENCPCP, AENBIND, AENPI
  APPN Network Node				ANNPRI, ANNSEC, ANNNEG, ANNCPCP, ANNBIND, ANNPI, ANNHPR
  Performance and Stress Testing		LU2B, LU2C, LU2G		LU62A: Basic & Mapped Conversations LU62C: Native Verbs & CPI-C

  After verifying your connection and correctly configuring SDTF as discussed above, make an initial testing run with all applicable SDTF libraries. Testing should start with the lowest SNA layer (link control) and finish with the highest layer (stress and performance).

  This initial testing run will allow you to get a quick idea of the functionality and stability of the IUT and identify any significant problem areas for immediate attention.

  As an example, consider a case in which SDTF is being used to test a 3270 LU2 display. These guidelines illustrate our recommended testing approach:

  • Refer to the supplied User Reference Manuals for instructions on running the individual test libraries as well as formal descriptions of the test functions.
  • Use SDTF log/trace file to record the results of the tests. Batch execution and the performance/stress tests also records results to a .PRN file. The .PRN files can imported directly into a spreadsheet program for analysis. You may choose to use the supplied Results Sheets or some other means of recording the pass/fail counts or performance of the tests you run.

  As in any testing situation, it is recommended that records be kept concerning all of the following:
  • physical environment and hardware -including baud rate and type of link,
  • SDTF and IUT version numbers,
  • configuration parameters for both SDTF and the IUT,
  • IUT 'hangs' (when system restart is required to continue), and
  • unexpected IUT results.

• In an SDLC environment, first run the Data Link Control (DLC) libraries with the IUT. If using a LAN or X.25 environment, skip to the next step. The DLC libraries are DLC, DLCA, and EFF74 test 001.

• Run the SNA Layer libraries with the IUT in the following order: PC, TC, SC, and DFC.

• Run SNAA, LU2B, LU2C, and LU2G to test Multi-PU and Multi-LU capabilities of the IUT, if desired. Other Multi-PU and Multi-LU tests will be executed by tests contained in the Display libraries.

• Run the libraries specific to the IUT. In this example of testing LU2 displays, run the tests within the Display libraries (LU2x). If you were testing a LU1/3 printer instead of a display, you would run tests from the Printer libraries at this step. The Display libraries include: BARTS, LU2A, LU2B, LU2C, LU2D, LU2E, LU2F, LU2G, and PS. The LU2B, LU2C and LU2G tests should be run last as they provide stress and performance testing. These tests may be used for single or multiple LU operation.

• After making a complete testing run with all appropriate libraries, compare the results you obtained with those of specific IBM implementations as shown in the supplied Results Analysis Manuals and the User Reference Manuals. The 3x74 VTC Results Analysis is located in the back of the Validation Test Plan / Validation Test Case User Reference Manual. The LU6.2 Results Analysis is located in the back of the LU6.2 User Reference Manual.

• Identify test libraries which ran in a significantly different manner than the IBM implementations. Run these test libraries again, with the SDTF Log/Trace active to destination FILE. Examine the Trace/Log files obtained to determine the reasons for the test failures. Make any appropriate product changes and re-test the IUT using the same libraries and configurations.

  The SDTF system also provides the user with the ability to validate the IUT's performance with respect to published architectures. The tester should be able to introduce variances into the product's environment. Examples of these variances include:

  • When using a different data rate, the IUT should be tested at the extremes. The SDTF test suites should be run at the lowest and the highest applicable data rates, and the tests should be consistent in their pass/fail counts.

  • The SDTF test suites should be run in different orders. As we suggested, the suites may be run from the lowest protocol levels, link control, to the highest level, presentation services.

  However, the IUT must also be able to run these tests in reverse or random order as well. The results obtained from running the tests in any order should not differ. Any differences should be investigated to determine the causes.

• Configuration settings on both SDTF and the IUT, such as:
  • OAF/DAF values and buffer sizes

  should be varied throughout the legal ranges of the IUT. The IUT should be tested with both minimum configuration options and maximum configuration options.

[ About ACT | Products | Services | Testing Information | Links | Download Demo | Jobs ]

Copyright © 1995,2000 Applied Computer Technology, Garland, TX USA (972)240-6744
Last Updated: Aug. 10, 2000 http://www.acomtech.com/howtotes.html