Advantage CA-Telon PWS supports the use of multiple macro.ini files to allow the loading and building of the customizable macros (TLNIIS, PGMNAMES and USREDITS) for different projects or applications.
Telon Interviews are getting tough these days as the technology grows faster. To get through the Telon interview one needs to update him/herself in a regular manner. Having said that, just before the interview, it is very important to have a quick glance of the reputed Telon questions and answers to make yourself comfortable during the interview process. This is where DoAnswers.com helps you in renewing yourself on Telon and various other technologies interview preparation.
21. I received a message that I can't access a specific member because it is in use by a user who left the company. Is there any way to delete these records without having all users log off of TDF and run the JCL to clean up the WIP files?
CA-Telon 4.0, at any genlevel, provides the ability to Zap these left over "LIVE" records through the TDF INSTALL menu. Once in the INSTALL menu, type in a LI for the function, and WF for the item. This will put you in the LIST/PURGE TDF WIP RECORDS panel, and list records on the TNTDFW file. Putting a "Z" to the left of the item that needs to be deleted will ZAP this record from the WIP files. A LI WD, or LI WX will display current WIP records on the TNTDDW, and TNTDDX files. Caution should be exercised here, so as not to DELETE a WIP record that really is in use by a current user that is currently logged on to the TDF.
22. I recently upgraded to CA-Telon 4.0. I now receive an "S806 REQUESTED MODULE TNFDMDLS NOT FOUND" when executing the CLIST to bring up the CA-Telon Design Facility. What is causing this system abend?
With CA-Telon 4.0, all CA-Telon PSBs were consolidated into one, TNFDMDL3. To eliminate the S806 abend, change the PSB name from TNFDMDLS to TNFDMDL3 in your personal CLIST. Alternatively, you may use the CLIST supplied with CA-Telon 4.0. This CLIST, @TDF, which is located in the INSTALL library, already includes a reference to TNFDMDL3 instead of TNFDMDLS. If you are using the CICS TDF and receive an AEI0 abend, add a program definition for TNFDMDL3 to your CICS region. The definition can be found in member TELON40 in the TABLES dataset on the 4.0 installation tape.
23. I tried to bring up the Advantage CA-Telon Design Facility release 4.0 with COBOL II libraries in the steplib and received a S0C4 abend. What caused this abend?
The Advantage CA-Telon Design Facility (TDF) release 4.0 requires at least Language Environment (LE) 1.5 or above. Running the TDF with an OS/VS COBOL or COBOL II runtime or with an LE runtime below version 1.5 will cause the S0C4 abend. We test the TDF with new versions of z/OS and OS/390 as they become available. As of May 2003, we have certified Advantage CA?Telon with LE 1.5 through z/OS 1.4, including 64-bit.
24. I updated my PGMNAMES for release 4.0 using the utility TLNUMKMC. When I looked at the new PGMNAMES, I noticed that the program header length definitions contained a macro variable as well as a number, for example &HDRLTH+2. What does this change mean?
When the TLNUMKMC utility creates a new version of the PGMNAMES macro, based on the contents of the #pdsqual.MACROINI file, the utility has no means of determining what the program header length might be, and therefore provides a generic method of accommodating any possible header length value (1 - 5). Thus, at generation time, if there is a 2-byte header and a 4-byte ID, then &HDRLTH will be calculated to contain a 2. This calculation can be seen in the PGMNAMES macro: in the STEP 3A area of code after label .GLOBAPP, the current header length contained in the global variable &SHEADER is calculated, and loaded into variable &HDRLTH. Note: this same feature exists in the Build Custom Macros process in CA-Telon/PWS.
25. I would like to upgrade CA-Telon to the latest genlevel, but how do I determine if I I should order a Maintenance Tape or a Product Tape.
CA-Telon maintenenance tapes are not cumulative; that is, each contains the product solutions only for the specified genlevel/service pack. The CA-Telon product tape is cumulative; in other words, it contains the entire product, including all of the product solutions published at the time it was produced. If you are at the "-1" genlevel -- the genlevel before the current one -- you should order a CA-Telon maintenance tape rather than the product tape. If you are at an older genlevel of the same release, you have the choice of applying each maintenance tape between the maintenance level you are on and the current genlevel, or reinstalling the entire product with the product tape. If you are changing releases, you must apply the CA-Telon product tape. Consider the following example: The current CA-Telon release/genlevel (or service pack) is CA-Telon 4.0, 0209 (SP2), the -1 release/genlevel (or service pack) is CA-Telon 4.0, 0112 (SP 1), and the base release is CA-Telon 4.0 genlevel 0106. If you currently have CA-Telon 4.0 genlevel 0112/SP1 installed, you can upgrade to CA-Telon 4.0 genlevel 0209/SP 2 by ordering the CA-Telon maintenance tape. If you are currently running CA-Telon 4.0 genlevel 0106/SP 1, you may either install both the genlevel 0112/SP 1 and genlevel 0209/SP 2 maintenance tapes, or install the CA-Telon 4.0 0209/SP 2 full product tape. If you are currently running a previous release of CA-Telon (such as CA-Telon 2.4), you would need to order the CA-Telon product tape.
26. I've just upgraded from CA-Telon 2.1 to 4.0, will I have the same generated results?
Not in all cases. There have been many enhancements and corrections to the CA-Telon product to make it function properly with newer versions of COBOL, IMS, CICS, and DB2. Many times these changes may produce different generated code that could result in different results. The results that you experience, although different, may be correct.
27. If I am upgrading CA-Telon releases, and I have the Data Administration Import DB2 Table option, will I have to recompile and bind TNMCDB2I for the new TDF?
You only have to rebuild TNMCDB2I if: 1. you change the DB2 subsystem you will be using with the CA-Telon TDF, or 2. the source for the TNMCDB2I program itself has been changed. Each subsystem is associated with a different DBRM library. If you change subsystems, you need to recompile and bind CA-Telon's TNMCDB2I DB2 interface program with a different PLAN pointing to a new DBRM, because the PLAN identifies the DBRM library. The source for TNMCDB2I (for COBOL language: #DB2ICOB for the TSO TDF and #DB2ICOC for the CICS TDF; for PL/I language: #DB2IPLC for the CICS TDF and #DB2IPLI for the TSO TDF) has changed in the upcoming release 4.0 (to allow for a maximum length of 32767 for VARCHAR columns), so it will be necessary to recompile and bind to pick up these changes.
28. In my previous TLNIIS macro, I had a single SETENV IMS. Now CA-Telon 4.0 TLNIIS has four SETENV IMS statements. Please explain.
In CA-Telon release 4.0, TLNIIS is set up with four occurrences of the "SETENV IMS" invocation. This allows CA-Telon users to specify a different SETENV invocation with separate parameter settings for four different types of IMS programs: Dynamic, Static, Driver and Report Definition. The global &PGMTYPE is assigned a value by the preprocessor program ADPCCARD, based on the type of "pgm" statement (e.g., IMSPGM, IMSDRV) and the value of LINKOPT, as described below: Program Type LINKOPT &PGMTYPE IMSPGM D IMSDYN IMSPGM S IMSSTAT IMSDRV n/a IMSDRV IMSPGM + REPORT n/a IMSRPT "IMSPGM" is the last macro statement in exported source for IMS programs (other than drivers). "IMSDRV" is the last macro statement in exported source for IMS driver programs. "REPORT" is one of the first macro statements for IMS Report definition programs. "LINKOPT" is a parameter on the IMSPGM macro that identifies the program as dynamic (D) or static (S).
29. In the Advantage CA-Telon PWS Macros menu, I make changes to SETSYS parameters, click OK, then run Build Custom Macros, but the changes do not appear in the new TLNIIS macro. What is wrong?
Most likely, you are pointing at the wrong macro.ini file when you the run Build Custom Macros utility. The macro.ini file updated by the changes you make to the TLNIIS, PGMNAMES and USREDITS notebooks is located in the \tlnusers\ folder under the PWS base directory, where "userid" is your user ID. This is also the macro.ini file updated when you execute the Load Custom Macros utility. Advantage CA-Telon PWS supports the use of multiple macro.ini files to allow the loading and building of the customizable macros (TLNIIS, PGMNAMES and USREDITS) for different projects or applications. However, the PWS Macro notebooks always make use of the macro.ini file found in \tlnusers\.
30. Is CA-Telon compatible with SHARK 2105 DASD?
CA-Telon is compatible with IBM's SHARK 2105 DASD.