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.
31. Is CA-Telon OS/390 compliant?
CA-Telon is OS/390 V1R1, V1R2, V1R3, V2R4, V2R5, V2R6, V2R7, V2R8, and V2R9 compatible. We suggest that you upgrade to the CA-Telon 4.0 release for OS/390 compatibility.
32. Manually customizing macros TLNIIS, PGMNAMES and USREDITS every time I install a new genlevel or release is time-consuming and error-prone. Isn't there an easier way to do it?
The 4.0 release of CA-Telon includes a new mainframe feature that allows you to modify the settings in those customizable macros without having to text-edit them manually. This new utility consists of two components: The first component takes an existing set of customizable macros and converts them to a single flat file. This file contains a list of easily modifiable parameter-value pairs listed under section headings (identified by curly brackets). So, for example, the SETSYS invocation in TLNIIS gets converted from this: SETSYS LANG=COB,OUTATTR=Y,REFRESH=Y,EOFKEY=Y,ALARM=N, X OUTIFIL=SPACE,? To this: {SETSYS} ALARM=N EOFKEY=Y LANG=COB LINEOPT=2 OUTATTR=Y OUTIFIL=SPACE REFRESH=Y This simple initialization file can be manually edited to change values as needed. The second component of the utility converts the parameter-value file back into the three customizable macros, ready for use with the Generator.
33. Our applications are in PL/1, does Casegen generate PL/1 ?
Yes. We have finished a beta test of Casegen for CICS PL/1, but have not yet decided whether to release it. The PL/1 IMS and batch products will be completed to special order, so please contact us if you are interested in any of these products and take a look at the COBOL product first to check out its capabilities.
34. We have customized Telon quite a lot, how does that affect Casegen ?
Customized Telon is no problem. We add the customizations to Casegen for you and then we support the customizations in future releases of Casegen. This means an end to your Telon support issues.
35. We use Telon LINEOPT 1 - is this supported.
Yes, Casegen will convert your LINEOPT 1 programs and provide exactly the same functionality in a COBOL program without Assembler subroutines. This is actually greater functionality than provided with Telon LINEOPT 2.
36. We would like to be able to display more than 99 pages in our CA-Telon segloop program. How do we implement this change?
These are the steps you need to follow: In TDF option 3, update the panel definition (PD) of the segloop program you want to change. If it has a PAGENO field, increase this field's length from 2 to 3 bytes. If you wish to increase the number of pages that can be paged backward before the first screen is redisplayed, update the segloop and change the PAGESAV number. (Note that this has no bearing on how many pages you can page forward.) This tells the Generator how large to make the PAGE-KEY-SAVE array. Update the TLNIIS macro you will use to generate the segloop program, and set PAGE999=Y. This tells the Generator to generate the PAGE-NUMBER-SAVE and PAGES-SAVED as two-digit fields. Increase the size of the PAGE-AREA-START variable in your XFERWKA custom code member, so that it is large enough to accommodate the larger PAGE NUMBER-SAVE and PAGES-SAVED, and the increased number in the PAGE-KEY-SAVE array, if you increased PAGESAV in step 2. Export, generate, precompile (if necessary), compile and link your program to create a new executable. If you are using IMS MFS or CICS BMS, you also need to regenerate and reassemble your CICS or IMS source.
37. What sort of COBOL does it generate ?
COBOL to the ANSI ?85 standard. This can be compiled by the COBOL-II or the COBOL/370 compiler or above. We are proud of the quality of the COBOL, and even IBM has commented favorably on its quality. Also, there are no Assembler subroutines - increasing the possibility of running the programs on multiple platforms.
38. When running the release 4.0 TDF running under CICS Transaction Server 1.3, we seem to go short on storage regularly. What can we do to prevent this?
The definition for the TNCPTDF program in TABLES member TELON40 marks the program as RELOAD(YES). To correct the problem, change the definition for program TNCPTDF in your CICS TS 1.3 region to RELOAD(NO). You can also change RELOAD(YES) to RELOAD(NO) on the TNCPTDF in the TELON40 member in the #pdsqual.TABLES PDS, then delete and reload the definitions. The change to the TELON40 member in #pdsqual.TABLES will be implemented in Release 4.0 Service Pack 3 (genlevel 0303).
39. When we run release 4.0 of CA-Telon PWS TDF with TDF database files on a network, response time degrades significantly when more than one user accesses the TDF. What can we do to improve response time?
Response time has been improved for CA-Telon PWS TDF with its database files residing on a network with the fix for problem 978 CA-Telon in Service Pack 2 (genlevel 0209). To improve response time even more, the following changes may be made to Btrieve registry settings: 1 DELETE LOCK FILE - DELETE TMP FILE - 0 2 CACHE ALLOCATION - CACHE SIZE - 4194304 3 OPERATION BUNDLE LIMIT - SYSTRANS BUNDLE LIMIT - 1 4 INITIATION TIMER LIMIT - SYSTRANS TIME LIMIT - 1 5 DISK I/O WAIT LIMIT - DISK WAIT LIMIT - 250 6 PAGE WRITE GROUP SIZE - PAGE GROUP SIZE - 5 These are the names and values under HKEY_LOCAL_MACHINE SOFTWARE BTRIEVE TECHNOLOGIES MICROKERNEL WORKSTATION ENGINE VERSION 6.15 SETTINGS
40. Why are CICS CA-Telon generated programs not case sensitive when using CA-Telon mapping?
Having CAPS=OFF does not always ensure that data will come from a screen into a CA-Telon-generated program with both upper- and lower-case characters. The following suggestions should help you receive case-sensitive data from your screen: In the TDF, on the Update Screen Parms panel (S112), set CAPS to OFF. In the PROFILE definition and TYPETERM definition of the terminal you are going to run the application from, set the UCTRAN (upper-case translation) parameter to NO.