Product: CA-Telon PWS
Version: 4.0, 4.1
OS: WIN98, WIN/NT, WIN2000, WINXP

Q: 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?

A: 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\<userid> 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\<userid>.

Product: CA-Telon
Version: 4.0 SP3, 4.1
OS: z/OS, OS/390

Product: CA-Telon PWS
Version: 4.0 SP3, 4.1
OS: WIN95, WIN98, WIN/NT, WIN2000, WINXP

Q: I noticed that significant changes were made to PGMNAMED (PGMNAMES) in release 4.0 servicepack 3 (genlevel 0303). Can we continue to use our current PGMNAMES, or do I need to recustomize the new version in order for it to work?

A: PGMNAMES is one of the customizable macros supplied with the Advantage CA-Telon Generator. It is used to customize the format for building the names of the programs, aliases, maps, etc. that you build with Advantage CA-Telon. In the past, if your shop used something other than the default of a 2-character header and 4-character ID, it was necessary to make changes to the calculations for the length of these components. With the changes in release 4.0 servicepack 3 (as well as release 4.1 base), we have streamlined the calculations so that they are done for you automatically. If you already have a customized copy of the release 4.0 or 4.1 PGMNAMES, you may continue to use it; you do not need to recustomize a copy of the new version.

Product: CA-Telon
Version: 4.0
OS: z/OS, OS/390

Q30: 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?

A30: 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.

Product: CA-Telon
Version: 4.0
OS: z/OS, OS/390

Q29: I installed a new CA-Telon service pack. On my first generation of a CA-Telon program, I receive the following message:
** ASMA057E Undefined operation code - TLNII/PGMNAMES. What am I doing wrong?

A29: CA-Telon service packs are shipped with a macro called PGMNAMED. As described in the CA-Telon Installation Guide, you need to make a copy of the macro PGMNAMED called PGMNAMES, then customize it to your shop's standards. This way, the original PGMNAMED is always maintained as a backup (in case you need to recustomize it). Once you have copied PGMNAMED to PGMNAMES, this ASMA057E error will no longer occur.

Product: CA-Telon
Version: 4.0
OS: z/OS, OS/390, WIN95, WIN98, WIN/NT, WIN2000, WINXP

Product: CA-Telon PWS
Version: 4.0
OS: z/OS, OS/390, WIN95, WIN98, WIN/NT, WIN2000, WINXP

Q: We would like to be able to display more than 99 pages in our CA-Telon segloop program. How do we implement this change?

A: 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.

1. 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.
2. 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.
3. 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.
4. 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.

A: 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).

Product: CA-Telon PWS
Release: 4.0
OS: WIN95, WIN98, WIN/NT, WIN2000, WINXP

Q: 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?

A: 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

Product: CA-Telon
Release: 4.0
OS: 0S/390

Q: 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.

A: 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.

Q: In my previous TLNIIS macro, I had a single SETENV IMS. Now CA-Telon 4.0 TLNIIS has four SETENV IMS statements. Please explain.

A: 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:

Q: 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?

A: 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.

Q: 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?

A: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.

Q: I just upgraded from CA-Telon 2.3 and now when I try to import or generate, I get lots of errors, including numerous severity-16 TLMSCR17 - INVALID OUTATTR VALUE "" SPECIFIED MNOTEs. What's wrong?

A: The most likely cause of these errors is that you are using an old copy the CA-Telon supplied import proc (TLNUMDEF), or old copies of one or more customizable macros -- TLNIIS, TELONIIS or PGMNAMES.

In release 2.4 (genlevels 9704 through 9906), much of the Generator set-up processing was streamlined, resulting in changes to both the CA-Telon Generator preprocessor (ADPCCARD, in the CONTROL step) and the Generator macros. These changes affect both Generator processing and Import, which goes through a "reverse-gen" step using the Generator. For this reason, it is essential that you always re-customize the JCL/procs and customizable macros supplied with each genlevel.

To determine if TLNUMDEF is causing the problem, check to see there is a CONTROL step (PGM=ADPCCARD) immediately before the GEN step. If you don't have a CONTROL step, then you are probably using an earlier version of the Import proc and will need to customize and use the version contained in the new #pdsqual.INSTALL PDS.

To determine if the problem is in the customizable macros, check for a "COPY PGMNAMES" statement in TLNIIS, or references to a global variable &INTIME in TLNIIS or TELONIIS. If you find any of these indications, you need to customize the versions of these macros from the latest genlevel. Also check to verify that the first statement in the PGMNAMES macro is MACRO. If it is not, then you are running with an old version of this macro and you must update it as well.

NOTE: your shop may use multiple versions of TLNIIS . If so, you will find references to them in your customized copy of TELONIIS. You will need to ensure that all of them are the current versions, as described above.

With release 4.0, we supply a new mainframe utility to make tailoring of the customizable macros easier; see Q18, dated 9/12/01, for specifics on this utility. (CA-Telon/PWS has a GUI customization utility as of release 3.0.) ”.

Q: 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?

A: 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.

Q: Does CA-Telon support HALDB (partitioned DBDs)?

A: Support for IBM's new IMS/ESA Partition Support Product, which (in IBM's words) "blows the 4GB lid" off HDAM and HIDAM databases, has been added to the latest CA-Telon release, 4.0. It is now possible to import DBDs that include PART (partition) invocations using CA-Telon's standard Database Import utility. Once imported, each PART is treated by CA-Telon as a DATASET. The code generated for DATASET data access works for PARTs as well. CA-Telon accepts all valid PART parameters (PARTL, DD1, DEVICE, MODEL, DD2, OVFLW, BLOCK, SIZE, RECORD, RECFM, SCAN, FRSPC, REL, ROOT, HIGHKEY), though it does not store or use PARTL, ROOT or HIGHKEY.

09/12/01

Q: 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?

A: 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.

Q: Does CA-Telon handle changes to a program's Custom Code when the modification is related to items such as a change in the environment, a change in Data Access, or an upgrade from OS/VS COBOL to COBOL for OS/390?

A: No. Although CA-Telon resolves user-written Custom Code in the appropriate place in a generated program, it never alters the content of the code. The programmer is responsible for making all changes to Custom Code.

Q: Why are CICS CA-Telon generated programs not case sensitive when using CA-Telon mapping?

A: 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:

1. In the TDF, on the Update Screen Parms panel (S112), set CAPS to OFF.

2. 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.

Q: 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?

A: 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.

Q: Why are our imports failing with the CA-Telon libararies?

A: All of your users most likely have have their own Import JCL. This JCL was was working fine with CA-Telon 2.1, and 2.3. Now since you have made CA-Telon 2.4 or 4.0 available to your users, imports using these libraries are failing. This is occurring because CA-Telon 2.4 introduced an extra step in the import procedure and this step is only compatible with the CA-Telon 2.4 libraries. The Import procedure that is created with the installation of Telon 2.4 or 4.0 needs to be used. This procedure is located in the PDSQUAL.INSTALL library. TLNUMDEF is the in-stream portion of the procedure, and JUMDEF, is the JCL execution of the procedure.

Q: Are CA-Telon maintenance genlevels cumulative?

A: Clients often call technical support wondering if the CA-Telon maintenance genlevels are cumulative. For example, "if I am running genlevel 9711, can I place maintenance genlevel 0006 right on top of it?" The answer to this question would be no. Only CA-Telon base product tapes are cumulative, not genlevel maintenance tapes. Note, however, that base product tapes are available at each genlevel and using a base product tape you can upgrade from any previous genlevel to the most current. It is required that you install your new CA-Telon base product tape into a new CSI (that does not have a previous CA-Telon 2.4 release), otherwise the target libraries will not get populated during the apply.

Q: I am trying to access a TDF member, but get the member in use by userid xxxxxxx message and when I try to re-import the same member I receive a TLMXI005 error. How can the member be in use when the user xxxxxxx is no longer logged on?

A: There is an active record on the WIP files and it needs to be deleted. Even though the employee has logged off of TSO or CICS, the users TDF session may have been terminated abnormally (i.e. the system may have gone down while the employee was accessing the member in question. To remove the live WIP record, go to the INSTALL panel by typing INSTALL on the Command Line of the TDF Main Menu. On the INSTALL panel, Enter LI WF and your CA-Telon password. Then on the List/Purge TDF WIP Records panel, ZAP the WIP file for the member that you need to access by placing a Z in the left-most column next to the member in question.

Q: Can I upgrade easily from CA-Telon 2.0 and/or 2.1 to 4.0?

A: Yes, just bring up your current TDF VSAM files with the new CA-Telon loadlib.

Q: I've just upgraded from CA-Telon 2.1 to 4.0, will I have the same generated results?

A: 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.

Q: Will CA-Telon support DB2 6.x?

A: CA-Telon does support DB2 6.x in tolerant mode. That is, we do not take advantage of any new features added in this release of DB2.

Q: Will CA-Telon operate under OS/390 V2 R10?

A: CA-Telon operates under all the OS/390 releases to date. If you are upgrading to an OS/390 release and running under a version of CA-Telon that is pre-4.0, we suggest that you upgrade to CA-Telon 4.0 as soon as possible.

Q: Is CA-Telon compatible with SHARK 2105 DASD?

A: CA-Telon is compatible with IBM's SHARK 2105 DASD.

Q: I am authorized for a specific set of CA-Telon components. In a recent mailing, I was sent the Product Authorizatons for all of my licensed CA-Telon components, but when I run the WLxxSPEC download job, all my licensed components are not listed. Why?

A: When performing CA-Telon maintenance installs, only the components that have had recent changes will be listed when you run WLxxSPEC. When the maintenance tape is shipped all the passwords that you are authorized for will be shipped with the tape. If you perform a full product install, the WLxxSPEC job would list all the CA-Telon components.

Q: Before I install the latest product maintenance tape that was sent to me, I would like to know what fixes are on the tape. How can I obtain this information?

A: You do not even have to install the product to get this list. If you unload file #9 from the tape, you will create a PDS that will include the member #FIXLIST. The PDS that will contain #FIXLIST is called SAMPJCL. The member #FIXLIST will define all the fixes that have been incorporated into this latest genlevel/service pack. NOTE: If you are performing a full product install (base install) for any genlevel, you will be considered to be at a new product base and will not receive the #FIXLIST file as the product is considered new to you.

Q: I am receiving U901 abend. What do I do?

A: The U901 abend is an internal CA-Telon abend which is returned when a TDF program encounters an error while attempting to perform I/O on a TDF file.

If a U901 abend occurs, run the JVERFY job to indentify and, optionally, delete the bad or missing blocks.

If you run JVERFY with the DELETE option, you might need to restore selected TDF members from your backups. To do this you must:

1. Define a set of temporary TDF files.
2. Reproduce your backup files into these temporary files.
3. Export the members that had been deleted through JVERFY DELETE.
4. Reimport the members into your permanent TDF files.

If you encountered errors while running JVERFY, reorganize your TDF files and reinitialize your WIP files; then rerun JVERFY.

Q: Is CA-Telon OS/390 compliant?

A: 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.

Q: I am trying to import a member and receive a TLMXI005 error message. How can I get around this message so I can import?

A: On the mainframe, the error is most likely caused by the member already existing in the WIP files. Running JREORGWK to delete, define, and reinitialize the WIP files takes care of this problem.

On the PC, go into the TDF and LI WF. If the program is there, ZAP it. This should solve the problem. However, on the PC, this problem can also be caused by the statement COPY USREDITS, in the EDITTBL macro. Remove the COPY so that the EDITTBL line reads only: USREDITS (starting in column 10).

Q: I am trying to access a TDF member, but get a member in use by userid xxxxxxx message. How can the member be in use, when the user xxxxxxx is no longer with my company?

A: There is a live record on the WIP files and it needs to be deleted. Go to the INSTALL panel and LI WF, then ZAP the member that you need to access. Even though the employee has been gone for a while, the TDF may have been exited abnormally, or the system may have crashed while the ex-employee was accessing the member in question.