How to transport Telon Screen Definitions (SDs) and programs in bulk via headers

Products

• Telon Application Generator

Issue/Introduction

When upgrading or migrating between Telon environments (e.g., from v4.0 to v5.1), users often need to move a large number of Screen Definitions (SDs) and associated programs. Exporting and importing each member individually is time-consuming. Users need a way to transport these objects in bulk using application headers.

Environment

Telon Application Generator Releases: 4.0, 5.1

Resolution

To transport programs and SDs in bulk, use the Telon Transport utility. This utility allows you to export all members associated with specific headers or even the entire TDF database.

Step 1: Identify Application Headers

Before performing the transport, list your headers to identify which ones to move:

1. Log into the Telon Design Facility (TDF).
2. From the Main Menu, enter INSTALL at the command prompt.
3. Select the option List application Header information to view all available headers.

Step 2: Bulk Transport-Out (Export)

Use the Transport-Out utility to create a transport file:

• JCL Member: JUTRANO or TLNOTRAN (located in the CAWLINST library).
• Control Cards: In the //TRANPORT.TPCTL DD * statement, use the HEADER parameter.
  
  
  

  TRANPORT EXPORTSELAUTOREFHEADER [YourHeaderName]END

  • Tip: Using EXPORTSELAUTOREF instead of EXPORTSELNOREF ensures that all referenced Data Administration entries (DB2/IMS definitions) are included in the transport file automatically.
  • Tip: To move everything at once, use TRANPORT EXPORTALL.

Step 3: Bulk Transport-In (Import)

Use the Transport-In utility to load the file into the target environment (e.g., v5.1):

• JCL Member: JUTRANI or TLNITRAN (located in the target CAWLINST library).
• Control Cards: In the //TRANPORT.TPCTL DD * statement, specify how to handle existing objects.
  
  
  

  TRANPORT IMPORTALLREPLACEEND

  • Options: Use IMPORTALLREPLACE to overwrite existing entries or IMPORTALLIGNORE to only add new ones

Additional Information

• 0901 ABEND: If the transport job fails with a 0901 ABEND, check for broken chains in the TDF (run JVERFY), custom code exceeding 2,000 lines, or insufficient VSAM space (run JREORGPR).
• Data Administration: When importing from 4.x to 5.x, ensure you use RUNTYPE=M (Merge) and MAXSEVR=12 in JUMDEF if moving Data Administration entries.