After creating an ACS routine, you must translate it into executable form. The translation process checks your source code for syntactic and semantic errors, generates an object form if no errors exist, and places the object form into the SCDS you specified on the translate panel. If the ACS routine that you are translating already exists in the SCDS, the new object form replaces the existing object form.

Before you begin: You must display the ACS Application Selection panel. See Creating ACS routines.

Perform the following steps to translate ACS routines.

1. Select option 2, Translate, from the ACS Application Selection panel. This displays the Translate ACS Routines panel.

   _______________________________________________________________

2. Supply values on the Translate ACS Routines panel:

   SCDS Name

   Is the name of an SCDS. A successful translation places the ACS routine object table into this SCDS. SCDS Name is primed with the last SCDS that you have referenced or translated into.

   ACS Source Data Set

   Is the name of the data set containing the ACS routine that you want to translate. This is a required field that is primed with the last used value.

   ACS Source Member

   Is the name of the member of the source data set that contains the ACS routine. It is required only if the ACS source data set is a partitioned data set or PDSE. The field is primed with the last used value. The default is blanks.

   Listing Data Set

   Is the name of a sequential data set to contain the translation results in Listing Data Set. If you specify a data set that already exists, the translation process replaces the existing data set contents with the results of the translation. If you specify a nonexistent data set, the translation process allocates space for it. If you leave this field blank, which is the default, you receive the results of the validation but you do not get a listing.