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.
11. Does it generate IMS Drivers ?
Yes.
12. Does it generate VSAM calls ?
Yes.
13. 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?
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.
14. I am receiving U901 abend. What do I do?
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.
15. 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?
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.
16. 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?
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.
17. I am trying to import a member and receive a TLMXI005 error message. How can I get around this message so I can import?
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).
18. 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? 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.
19. 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?
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.) ?.
20. 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?
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.