mainframes classes,materials,faqs,openings

ENDEVOR APPENDIX

2009-08-21T21:21:00.001-07:00

Appendix

NOTE: In the summary section of the sysout, you can tell which elements contained the search string because they will have a number (for the number of matches found) in the far right column - SCL WRITTEN. You can then go back to that section of the scan and find the lines where a match was found.

If you need to scan for many search strings across many Endevor systems (ACES, SUBRO, etc.), take a copy of OTXX94.ENDEVOR.SCANS(SCANALF) and edit it to meet your needs.

- The first statement is a "SET WHERE TEXT" statement that lists all the strings to be searched for. This "WHERE" statement is in effect for each "LIST" statement that follows.

- Next is the "SET OPTIONS" statement. Leave this as is. the "SHOW TEXT" clause causes the scan to show the lines where the search string is found which is necessary if you're searching for more than one string.

- Use the "LIST" statements to search many elements (by using a wildcard) of a particular type in an Endevor system.

In order to submit this SCL, go into Endevor Batch option (3) and specify your dataset in the REQUEST DATA SET section. Use option 3 to submit the scan, make sure the jobname is OTXX94# and that the MSGCLASS on the job card is J for $AVRS. The sysout will show only those elements where one of the search strings was found.

===> //OTXX94# JOB (44001,FS01,00000,1111),'PROJECT C583', => PROJECT NAME
===> // CLASS=A,MSGCLASS=J,NOTIFY=OT???? => YOUR ID
===> //*
===> //*$AVRS C=OTCACTSD =>(comment what program/linkcard/binddeck/sysin)

It's very important to use the proper project number in the jobcard, comment the project name in the comment field of the jobcard, notify your ID of job completion and use the $AVRS C= command to comment on what element you are adding/re-compiling/copying back...etc

ENDEVOR SCANS

2009-08-21T21:20:00.002-07:00

SCANS

1. From the Endevor Primary Options Menu, select 3 - BATCH.
(ENTER KEY).

2. Enter Option 1 - BUILD SCL.
Enter the name of the Request Data Set, e.g., OTXX94.LIB.CNTL(LIST).
Enter any job card changes needed.
(ENTER KEY).

3. Enter Option 11 - LIST ELEMENT.
(ENTER KEY).

4. Enter Option L - LIST element action.

Enter the FROM ENDEVOR INFO search criteria.

Enter the LIST OPTIONS criteria.
Note: Enter N in the Display List and Endevor selects and searches
all elements that fit the criteria entered in the FROM ENDEVOR INFO;

Enter Y in Display List and Endevor displays all
elements that fit the criteria entered in the FROM ENDEVOR INFO,
so that you must indicate which elements you wish to search, by
placing an L next to the member(s) to be included.

Enter the TEXT STRING to be scanned. (ENTER KEY).

5. A confirmation screen appears, listing the number of elements that were
selected for processing. Press the (ENTER KEY) to continue.

6. The message "SCL generated" appears, and Endevor displays the LIST ELEMENT ACTION screen.

7, Back out of the LIST ELEMENT ACTION screen.
(PF3 KEY).

8. Back out of the SCL GENERATION screen.
(PF3 KEY).

9. Select Option 3 - SUBMIT from the BATCH OPTIONS MENU screen.
(A batch job runs the scan.)
(ENTER KEY).

10. Once the batch job is completed, you can view the results in $AVRS. All elements
searched are listed on the output. If no match was found, the message is
'ELEMENT(S) BYPASSED, FAILED TO SATISFY "WHERE" CLAUSE'. If a match was found,
the element name and all the lines where a match was found are listed.

ENDEVOR NOTIFICATIONS

2009-08-21T21:20:00.001-07:00

NOTIFICATIONS
When your manager Receives/Reviews/Assigns a PROJECT:
1) The PROJECT Requestor
2) PROJECT Requestor's Supervisor
3) PMSO (Personal Market Support Operations)
RSIP (Risk Service Information Processes)
4) The Analyst to which the PROJECT is assigned
5) Business Market (for STAT Changes)
Personal Market (for STAT Changes)

When you start to work on a PROJECT, please notify the following people
to set Client TESTING and PRODUCTION implementation dates:
1) The PROJECT Requestor
2) The PROJECT Requestor's Supervisor
3) Your Project Leader
4) PMSO (Personal Market Support Operations)
RSIP (Risk Service Information Processes)
5) ACES on-call employees, Manager - IS
6) Business Market for STAT Changes
Personal Markets for STAT Changes
7) Look at Palinfo-Admin-Endevor-CHGNOTFY.XLS. There are several other groups that
must be notified if we make changes in ACES to certain designated programs. The
SCREEN CHANGE NOTIFICATION EXCEL Spreadsheet will identify the programs, that if
changed, will impact other groups, and who should be notified. The Project
Leader should contact these other groups at the very beginning of the project to
ensure that they have the appropriate time needed to make any necessary changes.

When you have completed your System Testing, please notify the following people:
1) The PROJECT Requestor
2) The PROJECT Requestor's Supervisor
3) Your Project (Personal Market Support Operations)
RSIP (Risk Service Information Processes)
4) On-call employees, Manager - IS

When Claims Systems completes their Client TESTING, clients should notify:
1) The PROJECT Requestor
2) The PROJECT Requestor's Supervisor
3) Your Project Leader
3) Individual PMSO contact (Personal Market Support Operations)
4) Individual RSIP contact (Risk Service Information Processes)
5) On-call employees, Manager - IS

A couple of days before the Production Implementation, please notify:
1) The PROJECT Requestor
2) The PROJECT Requestor's Supervisor
3) Your Project Leader
4) PMSO (Personal Market Support Operations)
(Risk Service Information Processes)
5) ACES Manager - IS and ACES SR. I/S Assistant (All changes)
6) Individual contact for Business Market changes
7) Individual contact for Personal Market changes

ENDEVOR BATCH (cont'd)

2009-08-21T21:19:00.002-07:00

BATCH (cont'd)

• If a proc that is part of the CA7 test cycle was changed to point to test versions of sysins, load modules, etc., that have subsequently been implemented into production, change the SYS1.PRODPROC member as needed to access the production components.

• If a new job was either added or had a scheduling change, update the constellation in PAL INFO/Hotbook/ACES Constellation

• If a new ISOT job was either added or had a change in the purpose, frequency or scheduling dependencies, update the document SERVER/PAL INFO/SUPPLEMENTAL HOTBOOK /ISOTLST.DOC.

• If a new batch program has been added, update the Batch Program Listing for new programs Pal Info \ Listprogdesc \Batchcbl.XLS.

• Delete proc member from signout document located in the current implementation folder.

• If a program results in an update, insert or delete to a propagated database or DB2 Table, update the DPROP Batch System Profile in Pal Info \ ACES \ Propagation Profile \ BTCHPROF.XLS.

ON-LINE
• Delete program from TDF if it was imported in.

• Cleanup your own libraries of MFS source code, format and referral members.

• If you had MFS changes, delete the format and referal members from IMSVSH.TFORMAT and IMSVSH.TREFERAL, using Aces panel Q.10 (option 5). Create the format and referal members for new MFS in 'OTXX94.TELON21.TFORMAT' and 'OTXX94.TELON21.TREFERAL' (used for BTS testing). Delete the OX version of the MFS source (used for the X system) from BATCH.PANLIB.

• Change IMST link map to refer back to the prod. library using Aces panel Q.7.11.2.

• SAVED FOR FUTURE INSTRUCTIONS REGARDING XPEDITER

• Run the IMST link using the production OBJ's using Aces panel Q.11.3.

• Run the IMST bind using Aces panel Q.14.1

• If a program change results in an update, insert or delete to a propagated Database or DB2 Table, update the DPROP Online System Profile in Pal Info \ ACES \ Propagation Profile \ ONLNPROF.XLS

• If a new online program has been added, update the Link group Document PAL INFO/
List Prog/ DESC/ Linkgrp.doc

ENDEVOR BATCH

2009-08-21T21:19:00.001-07:00

BATCH

• Ensure that the first two datasets in the STEPLIB DD of the test procedure are

//STEPLIB DD DSN=BATCH.OT.END.LOADLIB,DISP=SHR
// DD DSN=OTXX94.JOBLIBT,DISP=SHR
// DD DSN=PROD.OT.END.LOADLIB,DISP=SHR

If you have changed a dynamic subprogram, this will need to be done for all main programs calling this common subprogram dynamically.

If the test jcl procedure has not been set up this way, please change it and move the changed version to SYSTM1.ENDEVOR.PRODPROC.

• This following is for the test IKJEFT01 - SYSTSIN member only.

If the program is DB2 only running under IKJEFT01, change the SYSTSIN DD member in SYS1.JOBSYSIN from the old format

DSN SYSTEM(DB2T)
RUN PROGRAM(OTRDCATH) PLAN(OTRDCATH) LIB('OTXX94.JOBLIBT')
END

to a new format (if the plan name is the same as program name)

DSN SYSTEM(DB2T)
RUN PROGRAM(OTRDCATH)
END

or (if the plan name is different from the program name)

DSN SYSTEM(DB2T)
RUN PROGRAM(OTRDCATH) PLAN(OTXXXXXX)
END

• Delete the load from OTXX94.JOBLIBT (except for OTDPIMSP, OTDPDB2P, OTDB2CLM, and OTPOOL).

• If your program uses a link group, change IMST link map to refer back to the production library using Acespanel Q.7.11.10. Run the IMST link using the production OBJ's using Aces panel Q.11.4.

• Run a test bind to create the test plan using the production DBRM.

• Note: For procs that are part of the ACES CA7 test cycle, the following two
steps may already have occurred. See the 'Batch Change Checklist' document
for further clarification.
1) For any new sysin members where the Production and IMST version will be
different (i.e. the mailnote recipients), add the IMST version to SYS1.JOBSYSIN.
Make sure the IMST proc points to SYS1.JOBSYIN.
2) Move all the IMST procs to SYS1.PRODPROC.

ENDEVOR MISCELLANEOUS CLEANUP WORK

2009-08-21T21:18:00.002-07:00

MISCELLANEOUS CLEANUP WORK

Even if a system is in Endevor, you will still do development and testing outside of Endevor, therefore, it is still necessary to do this cleanup work.

COMMON(BATCH & ON-LINE)

• Delete any copybooks that went into production from 'OTXX94.COPYLIB.DATA'
Delete copylib member from located in the current implementation folder.

• Cleanup your own libraries of Source code, Copybooks, and DBRMS.

• If program has db2, delete any related DBRM's from 'OTXX94.LIB.DBRM'. OTDPIMSP, OTDPDB2P, OTDB2CLM, OTNICADP, and OTPOOL are the execptions to this rule. They are subprograms that get compiled/linked into both 'OTXX94.JOBLIBT' and 'PROD.OT.IMSLOADT' and bound into plans used by many link groups. If these members get deleted from the test DBRM library you will get a -818 timestamp error in any program accessing them. This is because the bind is using the production DBRM and the object module used to create the load member will still be the one from the last IMST compile/link. Therefore the timestamps in the OBJ and DBRM do not match, resulting in a DB2 return code of -818. Hence, don't delete these DBRMS (also, don't delete these load modules from 'OTXX94.JOBLIBT and 'PROD.OT.IMSLOADT').

• If a PSB was used in a new program or added to an existing program, update the PSB cross reference DB2 table, BATCHBOT.OTXPSBXT, with the production PSB information.

• Cleanup $avers after you get your jobs back. Be sure that all T, X and P jobs are deleted.

• If a new bind was either added or revised to use the IMS exit program or the DB2 exit program, update the DPROP Users Guide document by adding the bind to the List of Binds For IMS and DB2 Propagation under Nifty Things To Know in SERVER/PAL INFO/OVERVIEW/DPROP

• If a new bind was created, refer to Section XIII DB2 PROCEDURES Step D.

• If a new Follow-UP note was created, update the following documents:

SERVER/PAL INFO/OVERVIEW/FOLLOWUP/PGMTRACK.XLS
SERVER/PAL INFO/OVERVIEW/FOLLOWUP/WORKFLOW.XLS
SERVER/PAL INFO/OVERVIEW/FOLLOWUP/SEG VALUES.XLS

• If a new DB2 table, Database, ACES Table (TMS), Cobra File or Property File created update.
PAL INFO\DATABASE\ACES DATABASE & TMS SUMMARY

ENDEVOR EMERGENCY BATCH PRODUCTION UPDATES

2009-08-21T21:18:00.001-07:00

EMERGENCY BATCH PRODUCTION UPDATES

NOTE: These procedures are different because normally at night you will not have 2 Endevor approvers. So you will have to force the change to execute outside of Endevor and put it into Endevor the next day, if necessary.

If you are forcing a program into production at night here are some
things to remember/consider:

1. Compile the program using Q.2.1 specifying your own TSO library names
2. Check the job to be sure that it compiled clean. If necessary run a test if you have to on SYSC
3. Copy the appropriate binddeck needed to PROD.OT.PRODBIND
4. Edit the binddeck to point to your own TSO DBRM library name from the compile. You should place your dataset name ABOVE the PROD.OT.END.DBRMLIB and there should not be any other members in your library
5. Edit the job OTXX94.SYSG.DB2.CNTL(BIND).
6. Change the notify parameter to the ID that you are logged onto
7. Make sure it says XEQ NJEG to run on system G
8. Make sure the first exec statement is NOT commented (should be PROD.OT.PRODBIND) and the second exec statement IS commented (should be PROD.OT.PRODBBND).
9. Submit the job OTXX94.SYSG.DB2.CNTL(BIND) on system G.
10. Check the job in $avers to make sure the bind was successful.
11. Copy the related PROD proc to SYSTM1.ENDEVOR.TESTPROC and concatenate your TSO load dataset, defined in the compile, above the PROD.OT.END.LOADLIB. It is best to keep this module isolated therefore it needs to be the only one in your TSO load library.
12. Call the operator and ask them to restart the job with a step/restart if necessary.

ENDEVOR EMERGENCY ONLINE PRODUCTION UPDATES

2009-08-21T21:17:00.000-07:00

EMERGENCY ONLINE PRODUCTION UPDATES

If you are forcing a program into production during the day here are some
things to remember/consider:

1. Do you need to turn off screens? Stop transactions? Notify
Claims Systems/ACES-FSS-NCC Help desks/Tom Jost/Stat/Financial/Technical team?

2. Add the program to Endevor stage 1

3. Generate the linkcard using COPYBACK=Y

4. Move the element(s) to Endevor stage 2

5. Have Operations demand into CA7 OTONLNCP and/or OTBTCHCP and/or OTDBRMCP WITH OUT TRIGGERS to copy the members from the stage 2 libraries to production. Make sure yours are the only members in the stage 2 libraries first.

6. Run OTD2BIND and/or OTD2BBND WITHOUT TRIGGERS if necessary with the appropriate bind reset job following it. OTBINDRP follows OTD2BIND, OTBBNDRP
follows OTD2BBND - WITHOUT TRIGGERS.

7. Verify the MFS on all systems

8. Have IMS refresh the LLA & regions (BE SURE TO SPECIFY G & A)

NOTE: There is a timing issue between the bind and region refresh. If the new bind is done and the region refresh is not done right away, the load module will be out of sync with the application plan(s) and a -818 may occur. Similarly, if the region refresh is done and the bind is not done right away, the application plan(s) will be out of sync with the new load module and a -818 may occur.

9. Turn on screens, start transactions, test, notify the above

NOTE: MFS should NOT be forced in at all costs.

ENDEVOR BACKUP LINKS

2009-08-21T21:16:00.000-07:00

BACKUP LINKS

Whenever and element (COBOL, TELON, LINKCARD) is moved to Endevor stage 2 through a package, backups are done automatically by the move processor attached to the element. The backups are done as follows:

ELEMENT BACKUPS TAKEN
Batch non-DB2 (standalone link) LOAD
Batch DB2 (standalone link) DBRM, LOAD
Online non-DB2 no backup taken
Online DB2 DBRM
Online Link LOAD

The backups are made from the previous version of the member in the production library as follows:

PRODUCTION LIBRARY BACKUP LIBRARY
PROD.OT.END.LOADLIB PROD.OT.END.LOADLIB.BACKUP
PROD.OT.END.IMSLOAD PROD.OT.END.IMSLOAD.BACKUP
PROD.OT.END.DBRMLIB PROD.OT.END.DBRMLIB.BACKUP

XV. RESTORING PRODUCTION LOAD MODULES FROM BACK-UP

IT IS VERY IMPORTANT THAT YOU NOTIFY YOUR PROJECT LEADER AND/OR A MEMBER OF THE TECHNICAL TEAM BEFORE ATTEMPTING TO RESTORE FROM BACK-UP. THEY WILL BE ABLE TO ASSIST YOU AND MAKE SURE THAT A RESTORE IS NEEDED. ALWAYS CONSULT YOUR ANALYST AND/OR THE TECHNICAL TEAM BEFORE RESTORING FROM BACK-UP. THE SYSTEM MANAGER SHOULD ALSO BE NOTIFIED.

At this point, our backout procedures are still manual. We have looked into the Endevor backout, however, it only works if you are backing out your changes the same day you put them in and the elements are sitting in the stage 2 libraries. Once they have been moved to the production libraries, the Endevor backout does not work.

If your restore is not an emergency, you do not have to run the special jobs described below to copy the members from the backup libraries to the production libraries. In this case, you may simply follow the cleanup procedures outlined in step 6 to recompile/relink/move to stage 2.

NOTE: If an MFS change had been made you cannot use these procedures to restore from back-up. You will have to get together with your project leader and work out a solution.

1. Before attempting restore, it may be a good idea to save a copy of the existing production module. This will allow you to return to it if the module was needlessly restored.

2. Find the back-up files you have to restore. The back-up files are in the libraries:

PROD.OT.END.IMSLOAD.BACKUP
PROD.OT.END.LOADLIB.BACKUP
PROD.OT.END.DBRMLIB.BACKUP

NOTES:
All our systems, ACES, URS, Subro, FRACS, and Notes are backed up to these "OT" libraries.

The load modules that are copied to both the batch and online load library by the processor CIANBL47 are backed up only to PROD.OT.END.LOADLIB.BACKUP.

3. You will submit special jobs in order to copy the backed up members to the production libraries. There are jobsysin members (outside of Endevor) that you must update with the members you wish to restore.

The procs are in SYS1.PRODPROC; the jobsysins are in SYS1.JOBSYSIN; the jobs are in OTXX94.SPECIAL.JOBS. The names are as follows:

OTBKOLLD - Edit this jobsysin and run this job to restore online load modules.
OTBKBCLD - Edit this jobsysin and run this job to restore batch load modules.
OTBKDBRM - Edit this jobsysin and run this job to restore dbrms.

Once the job(s) run, check the newly copied members in the production libraries.
Remember that the new online modules will not appear until the LLA has been refreshed. See step 5 below.

4. A special bind job will have to be run if the module you are restoring has DB2 in it. You must copy the production binddeck to the dataset PROD.OT.PRODBIND. Be sure your entry is the only entry in the prodbind dataset. If it is not you will have to copy the other(s) to another dataset, run your special bind and then replace the previous entries after you run this special bind. The JCL to run this bind can be found in OTXX94.SYSG.DB2.CNTL(BIND). (The only thing that may need to be changed in this JCL is possibly the job name on the jobcard and the notify. It needs to run on G). Check the control cards before submitting the job. Check the job once it ends. The production binddecks for our systems are in the following libraries:

ACES - PROD.OT.END.BINDDECK
SUBRO - PROD.SU.END.BINDDECK Mudetail, Notes and URS have no DB2.
FRACS - PROD.FS.END.BINDDECK
ALF - PROD.OJ.LF.END.BINDDECK

NOTE: There is a timing issue between the bind and region refresh. If the new bind is done and the region refresh is not done right away, the load module will be out of sync with the application plan(s) and a -818 may occur. Similarly, if the region refresh is done and the bind is not done right away, the application plan(s) will be out of sync with the new load module and a -818 may occur.

5. For online restores call the TP room and have the production region refreshed and also an LLA refresh if the load library is under LLA control. You can check for LLA control by issuing a LISTQ command on system G against the PROD.OT.END.IMSLOAD library. If it is under LLA control the LISTQ will tell you that the library is in use by LLA.

The production regions are:

APPLICATIONS W/ TRANSACTIONS

SYSTEM EXECUTING IN REGION REGION
SYSTEM A ACES/FRACS/URS IMCLIFE1
IMCLIFE2
IMCLIFE3
SYSTEM G ACES/SUBRO/ADD CLAIM/NOTES/ALF/MUDETAIL
IF ANY OF THESE SYSTEMS REQUIRE A REGION REFRESH, REQUEST ALL OF SYSTEM G TO BE REFRESHED.

6. Cleanup - you may follow the procedures outlined above to quickly restore your systems to their previous state. However, it is important that all the pieces are in sync. It is important that we do not leave the "bad" source as the latest level in Endevor. As part of the cleanup, you should retrieve the previous version of source that you want to restore and add it back to Endevor using the procedures outlined in section V. This will create a new level of the element reflecting what is currently in production. If the element is associated with a link group, you must also re-link using the procedures outlined in section VII for linking an existing linkcard. You will then move the source and linkcard element(s) to stage 2 via a package.

ENDEVOR AUDATEX PROCEDURES

2009-08-21T21:15:00.002-07:00

AUDATEX PROCEDURES

Background: The following are the procedural changes that were created in response to DPROP development. As DPROP developed, and more DB2 was added to programs, it became clear that Audatex could experience some difficulty. Since the batch loads were copied from System C shortly after 4pm, but the batch bind job does not run until 8pm, the 6pm or 9pm Audatex run could run into mismatched links & binds. At the same time we started to look into this problem, it was decided that all Audatex runs for any day should run from the same load. The only reasonable way to solve both of these problems was to move the Audatex jobs from 'PROD.OT.BTCHLOAD' to 'PROD.OT.DI.IMSLOADP'. Since Endevor was installed, the Audatex jobs are now in 'PROD.OT.END.DI.IMSLOAD'. (When the programs are moved to Endevor Stage 2, they are temporarily loaded into PROD.OT.END.STAGE.LOADLIB; then OTBTCHCP copies them to PROD.OT.END.LOADLIB; then OTDILODP copies them to PROD.OT.END.DI.IMSLOAD, from which they execute -- although OTMISCED also executes from PROD.OT.END.LOADLIB via proc OTMISC1P.)

Now Audatex jobs execute from library 'PROD.OT.END.DI.IMSLOAD'. It is updated each morning between 5 and 6 am, which means that all 6 executions of the Audatex procs on a given day run with the same load modules. It also means that anyone making changes to the programs or the procs must proceed with caution.

These programs are included in Audatex processing:
OTMISCED, OT51B10, OT52B10, and OT54B10.

Use the following procedures when making changes to Audatex:

- Move programs to Endevor Stage 2 the DAY BEFORE the changes are to run for the first time.

- Make any proc changes between 6:30 and 10:00 AM the day AFTER PROGRAM CHANGES ARE MADE. (That is, the day the changes are to take effect.) With Endevor, you don't have to physically make the change at a set time:
just set up the production Package Execution Window to run at the appropriate time.

- If changes are made to OTMISCED, review the changes carefully to determine if there are any special considerations. Remember that OTMISCED runs in the batch cycle also, so from the evening it is moved to Endevor Stage 2, the batch cycle will run with the NEW version. This happens because the move action first puts the module into PROD.OT.END.STAGE.LOADLIB; then the external copy job, OTBTCHCP, runs between 7 and 8 PM, copying the contents of the stage load library to PROD.OT.END.LOADLIB. Some fancy footwork may be required to synchronize changes. (Note: this consideration existed prior to the change to PROD.OT.END.DI.IMSLOAD.) However, some of the footwork is
less fancy than before Endevor, because you can set the Package Execution Window to a time that suits your needs.

 The program OT55B10 (proc OTAURCVP) runs on system D and continues to run
out of PROD.OT.END.LOADLIB. This means that changes to this program take
effect for the 9 pm Audatex cycle. If this is not acceptable for a
specific change, the program may need to be 'forced' during the day.

ENDEVOR DISCHED AND DITABLE PROCEDURES

2009-08-21T21:15:00.001-07:00

DISCHED AND DITABLE PROCEDURES

Overview

These two DB2-only transactions are unique in that they are available to the field
for 23 hours a day, 6 days a week (6 X 23). They are retrieved from and moved to
Endevor in the usual way, but they are isolated in their own IMSG region (IMGPRODG).
When Endevor links the transactions, they are moved to PROD.OT.END.STAGE.IMSLOAD.
An external job, OTONLNCP, copies everything from the stage load library to
PROD.OT.END.IMSLOAD, the ACES online load library. However, since the DI members
must occupy their own region, another external job, OTDILODP, copies the DI members
from PROD.OT.END.IMSLOAD to PROD.OT.END.DI.IMSLOAD, from which they actually
execute. This job runs after IMSG is brought down, between 5 and 6 in the morning.

MFS

The normal MFS test-t-prod procedures should be followed. Screen format changes can create problems since the format library flip happens at around midnight, Monday through Friday, and at 5:00 PM on Saturdays. Additionally, the TP room should be notified to stop the transaction (DISCHED or DITABLE) at midnight that weeknight.

DB2 Binds (System G)

Production binds should be done each time a new load module is created regardless of whether SQL has been changed.

When you relink either DI load module and move it back into Stage 2 (production), in addition to moving the load to the correct production load library, Endevor sets up the input to the production bind. It takes the appropriate Endevor DI binddeck member and loads it into the sequential dataset, PROD.OT.DI.PRODBIND. This is input to the bind job, OTD2BDIP. This process ensures that a production bind is done each time either DI load module has changed.

Verification (System G)

1. Check job OTDILODP in $AVRS to make sure the load module was copied to
PROD.OT.END.DI.IMSLOAD.

2. Check job OTD2BDIP to make sure the bind was successful.

Note: Both of these jobs run when IMSG is brought down between 5:00 AM and 6:15 AM the following day.

ENDEVOR PRODUCTION

2009-08-21T21:14:00.000-07:00

PRODUCTION

Forcing a BIND into production during the nightly joblog schedule:

Use this process when making changes to DB2 sub-programs like OTDPDB2P which has numerous BINDS associated with it but the ENDEVOR processor does not automatically stage the proper binds for all plans related to it during the package move.

GENERATE the BINDDECK Element with COPYBACK=Y.
(Option 4 - Generate, from the BATCH OPTIONS MENU).
E - Endevor or 3.PP.E
4 - Claims
3 - Batch
1 - Build SCL
4 - Generate (example follows)

NOTE: Make sure you change COPYBACK (under ACTION OPTIONS) from 'N' to 'Y'. Also be sure to choose the appropriate processor for either a Batch bind or an Online bind.

----------------------------- GENERATE ELEMENTS -----------------------------
OPTION ===> g
ELEMENT DISPLAY OPTIONS:
blank - Element list S - Summary B - Browse H - History
G - Generate element M - Master C - Changes

FROM ENDEVOR: ACTION OPTIONS:
ENVIRONMENT ===> CLAIMS CCID ===>
SYSTEM ===> ACES COPYBACK ===> Y (Y/N)
SUBSYSTEM ===> ACES OVERRIDE SIGNOUT ===> N (Y/N)
ELEMENT ===> OTxxxxxx PROCESSOR GROUP ===> BINDxxxx
TYPE ===> BINDDECK
STAGE ===> U U - CLAIMSU C - CLAIMSC

COMMENT ===>

LIST OPTIONS:
DISPLAY LIST ===> Y (Y/N)
WHERE CCID EQ ===>
WHERE PROC GRP EQ ===>
BUILD USING MAP ===> N (Y/N)
-------------------------------------------------------------------------------
NOTE: Setting COPYBACK=Y copies the latest version of the BINDDECK to stage U. You must still do a separate package move to put the BINDDECK element back into stage C. This will also move the binddeck to the proper staging library (Online or Batch).

*** Select a PROCESSOR GROUP. *** THIS IS A VERY IMPORTANT STEP ! !
To assign a Processor Group, type a processor name next to PROCESSOR GROUP
(under ACTION OPTIONS above) or type an '*', which will list three processors
for type BINDDECK. When the list is displayed, place an "S" next to the
appropriate processor and hit enter. (DO NOT select the *NOPROC* processor)

BINDBTCH - Stages to the PROD.OT.END.STAGE.BTCHBIND OTD2BBND 8:00pm M-F
BINDONLN - Stages to the PROD.OT.END.STAGE.ONLBIND OTD2BIND 11:00pm M-F, 4pm Sat

ENDEVOR DB2 PROCEDURES

2009-08-21T21:13:00.000-07:00

DB2 PROCEDURES

As part of normal production procedures, Endevor takes care of setting up your binds. When you move a DB2 load module to Endevor stage 2, the bind statements (from PROD.XX.END.BINDDECK where XX denotes the system that the bind cards belong to) for that load module are copied to the correct bind stageing library; PROD.OT.END.STAGE.ONLBIND for online, and PROD.OT.END.STAGE.BTCHBIND for batch. The binds execute on system G. This is true for ACES and SUBRO. FRACS binds need to execute on system A, so its binddecks are copied to PROD.FS.END.STAGE.ONLBIND or PROD.FS.END.STAGE.BTCHBIND.Drive-in App binddecks are copied to PROD.OT.DI.PRODBIND.

DB2 Binds (System G)

There exist four procs that run during the nightly batch cycle that handle
the Binds and Grants and cleanup. They are;

OTD2BIND for On-line & Nonconversational programs. (Executes a Bind & Grant)
OTBINDRP empties out PROD.OT.END.STAGE.ONLBIND
OTD2BBND for Batch programs. (Executes a Bind only).
OTBBNDRP empties out PROD.OT.END.STAGE.BTCHBIND

DB2 Binds (System A)

There exist four procs that run during the nightly batch cycle that handle
the Binds and cleanup. They are;

FSD2BIND for On-line & Nonconversational programs.
FSBINDRP empties out PROD.FS.END.STAGE.ONLBIND
FSD2BBND for Batch programs.
FSBBNDRP empties out PROD.FS.END.STAGE.BTCHBIND

Production binds should be done each time a new load module is created regardless of whether SQL has been changed. Endevor will take care of this for you; you just need to verify that the binddeck(s) have been copied after your move.

Follow the next 5 steps if adding a plan or changing a binddeck:
A. Create bind control cards for plan using generic bind control cards
OTXX94.DB2.BINDCARD(BINDCARD). The new bind control cards should be named the
same as the plan name. Replace XXXXXXXX with the plan name and replace the
YYYYYYYY entries with the correct member names. Be sure that the ACTION
parameter is always REPLACE. REPLACE will always work, even the first time.
The LIBRARY statement may need to have DPROP and XS libraries added. The complete concatenation order is:
LIBRARY (‘SYS1.DPROP.EKYDBRM’ +
‘PROD.OT.END.DBRMLIB’ -
‘PROD.XS.DS.OT.SRVS.DBRMLIB’) -

B. FIRST TIME: Grants: On-line and Nonconversational Programs ONLY:
Edit PROD.OT.PRODGRNT and copy the generic GRANT card from OTXX94.DB2.BINDCARD(GRANT). The Generic GRANT card is as follows:
GRANT EXECUTE ON PLAN XXXXXXXX TO PUBLIC ;
Replace XXXXXXXX with the desired plan name and save dataset. Remember that
other programmers may be doing a GRANT that night so you should copy your
GRANT cards after theirs.
C. Add the BINDDECK to Endevor using a processor group of *NOPROC*. Follow the procedures outlined for adding a linkcard for the first time in section V.3.

D. Update the appropriate binddeck for the system being changed: IE: OTBNDBAT
binds all plans in the ACES Batch system. OTBNDONL binds all ONLINE plans. The
prefixes used are FS, OJ & SU for FRACS, ALF & SUBRO. ALF only uses the
OJBNDBAT member since no online transactions use DB2.
Note: OTBNDBAT and OTBNDONL are only used if all ACES plans need to have BINDs run.

E. Update the DRPROP document found on PALINFO\OVERVIEW\DPROP. Go to page 22
under Nifty Things to Know and update either the table for IMS and DB2
propagation or the table for DB2 only propagation.

NOTE: You need to do this before you move your programs to Endevor stage 2. This is because the move processor will look for the bindcards to copy to the bind stageing library. If it is not there, the processor will get an error and your bind will not be set up.

Verification (System G)

If the bind was done for an On-line program then check job OTD2BIND or FSDBBIND in $AVRS on system G the following day.

If the bind was done for a Batch program then check job OTD2BBND or FSD2BBND in $AVRS on system G the following day.

Emergency Binds

There is JCL in OTXX94.SYSG.DB2.CNTL(BIND) to submit a bind immediately. The procedure is different from the normal bind procedure because Endevor normally does it automatically for you. A good reason for doing this would be a -818 abend (timestamp discrepancies between plan and load module). Please consult your project leader or someone on the technical team if you think this might be necessary. Copy the bindcards from PROD.XX.END.BINDDECK (where XX denotes the system they're associated with) into PROD.OT.BBNDBIND or PROD.OT.PRODBIND. Check that the library statement points to the proper DBRMs. Run the job and check the output in $AVRS.

Adding from Stage C to Stage 2

2009-08-21T21:12:00.000-07:00

Adding from Stage C to Stage 2
Using the name of your package (when you moved from Stage U to Stage C):

E - Endevor or 3.PP.E
5 - Claims
4 - Package
9 - Utilities

----------------------------- Package Utilities ------------------------------
Option ===> R

D - Display Package R - Reset Package
E - Export Package # - Delete Package

PACKAGE ID: OTDH94072199A STATUS: EXECUTED
DESCRIPTION: OTCOLFSD/F8
PACKAGE TYPE: STANDARD

TO ISPF LIBRARY:
PROJECT ===> OTDH94 REPLACE MEMBER ===> N (Y/N)
GROUP ===> SCL
TYPE ===> CNTL
MEMBER ===>

OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>

ENTER

----------------------------- Package Utilities ---------------- PACKAGE RESET
Option ===>

D - Display Package R - Reset Package
E - Export Package # - Delete Package

PACKAGE ID: OTDH94072199A STATUS: IN-EDIT
DESCRIPTION: OTCOLFSD/F8
PACKAGE TYPE: STANDARD

TO ISPF LIBRARY:
PROJECT ===> OTDH94 REPLACE MEMBER ===> N (Y/N)
GROUP ===> SCL
TYPE ===> CNTL
MEMBER ===>

OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>

PF3

---------------------- Package Foreground Options Menu ------------------------
Option ===> 2

1 DISPLAY - Display Package Information
2 CREATE/MODIFY - Create or Modify Package
3 CAST - Prepare Package for Review
4 REVIEW - Approve or Deny Package
5 EXECUTE - Submit or Execute Package
6 SHIP - Ship Packages
7 BACKOUT - Perform Backout or Backin Processing
8 COMMIT - Clear Backout Information
9 UTILITIES - Reset, Delete, or Export Package
L DistribuLink - Perform Product Collection Request

Package ID ===> OTDH94072199A

Limit selection list by Package Status. These are used by the DISPLAY
and UTILITIES options:

In-Edit......... Y In-Execution.... Y
In-Approval..... Y Executed........ Y
Denied.......... Y Committed....... Y
Approved........ Y

MODIFY -------------------- CREATE/MODIFY PACKAGE -----------------------------
OPTION ===> E

B - Build Package Actions I - Import SCL
E - Edit Package C - Copy Package
N - Add Notes to Package

PACKAGE ID: OTDH94072199A STATUS: IN-EDIT
DESCRIPTION ===> OTCOLFSD/F8
PACKAGE TYPE ===> STANDARD
SHARABLE PACKAGE ===> N (Y/N) APPEND TO PACKAGE ===> N (Y/N)
ENABLE BACKOUT ===> N (Y/N)
EXECUTION WINDOW FROM ===> 21JUL99 00:00 TO ===> 31DEC79 00:00

INPUT PACKAGE ID ===>

FROM ISPF LIBRARY:
PROJECT ===> OTDH94
GROUP ===> SCL
TYPE ===> CNTL
MEMBER ===>

OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>

CHANGE ALL STAGE U TO STAGE C, THEN PF3

---------------------- Package Foreground Options Menu ------------------------
Option ===> 3

1 DISPLAY - Display Package Information
2 CREATE/MODIFY - Create or Modify Package
3 CAST - Prepare Package for Review
4 REVIEW - Approve or Deny Package
5 EXECUTE - Submit or Execute Package
6 SHIP - Ship Packages
7 BACKOUT - Perform Backout or Backin Processing
8 COMMIT - Clear Backout Information
9 UTILITIES - Reset, Delete, or Export Package
L DistribuLink - Perform Product Collection Request

Package ID ===> OTDH94072199A

Limit selection list by Package Status. These are used by the DISPLAY
and UTILITIES options:

In-Edit......... Y In-Execution.... Y
In-Approval..... Y Executed........ Y
Denied.......... Y Committed....... Y
Approved........ Y

CAST -------------------------- CAST PACKAGE ----------------------------------
OPTION ===> C

C - Cast Package S - Display SCL
N - Add Notes to Package

PACKAGE ID: OTDH94072199A STATUS: IN-EDIT
DESCRIPTION: OTCOLFSD/F8
PACKAGE TYPE: STANDARD
SHARABLE PACKAGE: N
VALIDATE COMPONENTS ===> N (Y/N/W)
ENABLE BACKOUT ===> N (Y/N)
EXECUTION WINDOW FROM ===> 21JUL99 00:00 TO ===> 31DEC79 00:00

USER ID DATE TIME
CREATED: OTDH94 21JUL99 11:01
LAST UPDATED:

CAST -------------------------- CAST PACKAGE ----------------------------------
OPTION ===> CAST SUCCESSFUL

C - Cast Package S - Display SCL
N - Add Notes to Package

PACKAGE ID: OTDH94072199A STATUS: IN-EDIT
DESCRIPTION: OTCOLFSD/F8
PACKAGE TYPE: STANDARD
SHARABLE PACKAGE: N
VALIDATE COMPONENTS ===> N (Y/N/W)
ENABLE BACKOUT ===> N (Y/N)
EXECUTION WINDOW FROM ===> 21JUL99 00:00 TO ===> 31DEC79 00:00

USER ID DATE TIME
CREATED: OTDH94 21JUL99 11:01
LAST UPDATED:

Send a note to two approvers for completion of implementation…

ENDEVOR MFS UPDATES

2009-08-21T21:11:00.000-07:00

MFS UPDATES

The following paragraphs outline the procedures for implementing
MFS members:

- MFS changes should be made only on Friday.

- Retrieve the member from Endevor Stage 2 to yourid.LIB.SOURCE or your own
PDS - this version is basically discarded. A new MFS will be generated
EXCEPT for MFS members: OTR01AMF and OTR31AMF. For OTR01AMF and OTR31AMF
changes, you will edit the MFS directly and not generate a new MFS through
panel Q.10 (TELON 2.1 MFSGEN SECTION MENU).

- Perform the necessary changes to the MFS. This may mean utilizing TDF or
other methods of changing the source code and testing the changes (refer to online testing document on Aces server PAL INFO\CHKLIST\ONLINTST.DOC).

(1) Add the MFS member from your PDS or yourid.LIB.SOURCE to Endevor Stage U, using either FOREGROUND (Option 2 from the Endevor Primary Options Menu) or BATCH (Option 3). BE SURE TO SPECIFY MFSGEN FOR THE PROCESSOR GROUP.

(2) Move it to Endevor Stage C (see sections V.7.a through f).
(along with the associated program change).

(3) Begin Testing.

(4) Add the MFS to production

(5) The move processor will update the DSN 'IMSVSP.MFSBATCH'. This
library is copied to the appropriate systems nightly by an IMS job. The MFS change does not go into effect until the following day. The program
TTPRODS and links will have to be done at the same time so the program
and MFS is not out of sync.

NOTE: IMSVSP.MFSBATCH on system C is copied to a stageing library IMSVSP.FORMAT by IMS job IMHFORMT which runs on system C. This library is accessible to all systems. Then a job on each system runs to copy MFSs from the stageing library (IMSVSP.FORMAT) to the appropriate offline MFS library (IMSVSP.FORMATA or IMSVSP.FORMATB). For example, the job that runs on system G is called IMGFORMT, on system A IMAFORMT, etc. Then the IMSVSP.FORMATA and IMSVSP.FORMATB libraries are swapped so the newest changes are brought online.

Test = generate MFS and format using Q panels (Q.10) *existing way

***Moving MFS with program for purpose of production package.
- When doing 'X' and 'P' MFSGENS there are a few things to look for to double
and triple check your jobs. These days we can't be too careful.

1). Go to 3.PP.D.1 and look at the dataset named 'IMSVSP.MFSBATCH'.
This dataset should be empty unless someone else in the area has
done an MFSGEN that day for 'X' or 'P'.

2). Once the 'SYSC MFS' job has finished, max down to the bottom to
be sure that the correct version of MFS was generated. Located at
the bottom left hand corner of the sysout you should see the
MFS program name. If the MFSGEN was for 'X' the name should be
OXOPPPP (where PPPP is the program name). If the MFSGEN was for
'P' the name should be OTOPPPP.

3). Do a "F 'DEVICE MAPPING' PREV" in the sysout to see a copy of
the screen image. Be sure that the field that you added, changed
or deleted is where it should or shouldn't be.
4). Go back to 3.PP.D.1 and look at the dataset named 'IMSVSP.MFSBATCH'.
This dataset should now have approximately 6 lines related to the
MFSGEN that was submitted.

- First thing the next morning, check the MFS gens in production by issuing
the /FOR (modname) command. Check all systems.

BOCOMP CAPS IMS IMSG IMST

- Be sure to print your package from $AVRS.

- File the production gens in the production cabinet and throw away the old
versions.

- Hold onto the T system gens along with the testing results of the change.

- Delete the job from $AVRS.

- Send a MAIL NOTE to everyone so that they know they don't need to use /TEST
MFS any more.

ENDEVOR UTL (JOBSYSIN) UPDATES

2009-08-21T21:10:00.000-07:00

UTL (JOBSYSIN) UPDATES

All production members of type UTL (jobsysins, etc) reside in PROD.XX.END.JOBSYSIN (where XX denotes the system the jobsysin is associated with). The following paragraphs outline how to implement UTLs into production.

- Retrieve the UTL from Endevor to yourid.LIB.JOBSYSIN.

- Make the necessary changes.
- Add the UTL from the PDS to Endevor Stage U. You can use FOREGROUND
(Option 2 from the Endevor Primary Options Menu). If adding a new jobsysin,
you must specify processor group *NOPROC*. The former processor group UTL is
not available in the CLAIMST environment.

- Move the UTL from Endevor Stage U to Endevor Stage C, using package
processing (see sections V.7.a through f).

- Begin Testing.

- Add the UTL to production.

- A hard copy printout is not needed. One can browse Endevor to see the most
recent member.

ENDEVOR PROC UPDATES

2009-08-21T21:09:00.000-07:00

PROC UPDATES

All production procs reside in SYSTM1.ENDEVOR.PRODPROC on System C - Endevor
Stage 2. The procedures for implementing production procs are as follows.

 Sign out the PROC in the signout document located in the current
implementation folder.

 Retrieve the proc from Endevor Stage 2 to yourid.LIB.CNTL (or library
of your choice).

- Make the necessary changes.

- Refer to the Disaster Recovery section of the NEWPROC.DOC located in
PAL INFO\CHKLIST on page 3. THIS IS A CRITICAL STEP!!

- Move the proc from the PDS to SYS1.TESTPROC (option 3.3). Be careful not to overlay anyone else's changes. NOTE: Never make changes in SYS1.TESTPROC.

- Add the proc from the SYS1.TESTPROC to Endevor Stage U. You can use
FOREGROUND (Option 2 from the Endevor Primary Options Menu).

- Move the proc from Endevor Stage U to Endevor Stage C, using package
processing (see sections V.7.a through f).

- Test the changed proc. (At the very least do a scan.) Use P=PROC01
on the JOBPARM card to point to SYS1.TESTPROC.

- Add the proc to production.

- Sign the proc back in using the proc signout document
located in the current implementation folder.

ENDEVOR UPDATES

2009-08-21T21:07:00.000-07:00

All production copylib members are located in SYSTM1.ENDEVOR.COPYLIB on System C -
Endevor Stage 2. The following outlines the procedures for implementing
COPYLIB changes.

 Sign the COPYLIB member out in signout document located in the current
implementation folder.

- Determine all programs that use the changing COPYLIB member. (An Endevor
scan flags the programs using the copybook; see section XX. Be aware
that these scans will not find references to the "Telon generated" copybook
references such as OTTMUPDA and OTTMWORK.)

- Notify ACES team via MAIL NOTE in a timely manner. You should identify what
source members are involved, what the change involves, Project number (if
applicable), when the change will be implemented, and any other pertinent
information.

- Retrieve the COPYBOOK Element from Stage 2 Endevor to OTXX94.COPYLIB.DATA.
Be careful not to overlay anyone else's changes.

- Make the change (refer to the online testing document on Aces
server PAL INFO\CHKLIST\ONLINTST.DOC).

- ADD the COPYBOOK Element to Endevor Stage U. You can do this using
FOREGROUND (Option 2 from the Endevor Primary Options Menu). Copybooks are
added as *NOPROC* in the mapped environment.

- REGENERATE any affected programs to Endevor Stage U (for information on how to do this, see section VI.1, above) to pick up the new copybook. You may
also need to relink.

- MOVE any affected Elements (programs and copybooks) to Endevor Stage C
(package processing) Bind (Q.14) where necessary.

- Begin Testing.

- Move to production.

- A hard copy of the copy member is not needed. One can see the most
recent version by browsing Endevor Stage 2.

- Send a MAIL NOTE notifying ACES team when the change is complete.

ENDEVOR STATIC LINK PROCESSOR GROUPS

2009-08-21T21:06:00.000-07:00

STATIC LINK PROCESSOR GROUPS:

For an electronic version of ACES LINK Process Groups: See 5f

b. Submit the job.

c. When the job has completed, check $AVRS (3.pp.$).

d. Move the LINKCARD Element to Stage C. This is the same as package processing for programs; for more detail, see sections V.7.a through f, above.

e. When the package job has completed, check SDSF to verify that the load module is now in the appropriate stage C library.

ENDEVOR LINKCARD

2009-08-21T21:05:00.000-07:00

Generating an unchanged LINKCARD

a. GENERATE the LINKCARD Element with COPYBACK=Y. (Option 4 - Generate,
from the BATCH OPTIONS MENU).

E - Endevor or 3.PP.E
4 - Claimst
3 - Batch
1 - Build SCL
4 - Generate (example follows)

NOTE: Make sure you change COPYBACK (under ACTION OPTIONS) from 'N' to
'Y' (see example below).

----------------------------- GENERATE ELEMENTS -----------------------------
OPTION ===> g
ELEMENT DISPLAY OPTIONS:
blank - Element list S - Summary B - Browse H - History
G - Generate element M - Master C - Changes

FROM ENDEVOR: ACTION OPTIONS:
ENVIRONMENT ===> CLAIMST CCID ===>
SYSTEM ===> ACES COPYBACK ===> Y (Y/N)
SUBSYSTEM ===> ACES OVERRIDE SIGNOUT ===> N (Y/N)
ELEMENT ===> otxxxxxx PROCESSOR GROUP ===>
TYPE ===> LINKCARD
STAGE ===> U U - CLAIMSU C - CLAIMSC
CLAIMSU OR CLAIMSC = “From where you want to run the generate”
COMMENT ===>

LIST OPTIONS:
DISPLAY LIST ===> Y (Y/N)
WHERE CCID EQ ===>
WHERE PROC GRP EQ ===>
BUILD USING MAP ===> Y (Y/N)

-------------------------------------------------------------------------------
NOTE: Setting COPYBACK =‘Y’ will locate the source for the generate, which will be from Stage U, C, 1, 2 (in that order). You must still do a separate package move to put the linkcard element back into stage C. Build using map = ‘Y’ for Stage 2 source “From Endevor” means from where do you want to execute the generate processor, NOT from where is the source.

Select a PROCESSOR GROUP.

To assign a Processor Group, type next to PROCESSOR GROUP
(under ACTION OPTIONS):

• one of the processor group names or '*', which the entire list
of Processors for type LINKCARD. When the list is displayed, place
an "S" next to the appropriate processor and hit enter.

ENDEVOR LINKS

2009-08-21T21:04:00.000-07:00

Linking a program creates a load member in the appropriate Endevor Stage U load library and saves the link edit listing. If the program is standalone, the link occurs during the GENERATE process -- that is, when you ADD it to Stage U or do a GENERATE WITH COPYBACK into Stage U, you are compiling and linking the program; therefore, to put this kind of program into production, nothing more is needed than outlined in the section V, above. But if the program must be linked with other application modules, the link must be done as a separate step, using linkcards. Currently, all online programs use linkcards.

When the element (program or linkcard) is moved to Endevor stage C via a package, the load module is moved from the Stage U load library to the appropriate Stage C libarary - BATCH.OT.END.LOADLIB (for batch programs) or PROD.OT.END.IMSLOADT (for online programs).

1. LINKCARDS.

Endevor has LINKCARDS for every STATIC circle. The linkcards are in PROD.OT.END.LINKCTL or PROD.OJ.LF.END.LINKCTL and contain the INCLUDE statements for every OBJ member in a static circle.

The LINKCARDS and their associated link PROCESSOR GROUPS ARE LOCATED N 5f OF THIS DOCUMENT. (Explanation and/or view listing of the processor groups).

2. LINK AN EXISTING LINKCARD (MOST COMMON SCENARIO).

a. The obj concatenation order is Stage U, Stage C, Stage 1, and Stage 2. Make
sure you are including obj’s from the correct libraries.

b. If you are making CHANGES to the linkcard, retrieve it from Stage C
to yourid.LIB.LINK (or library of your choice)and complete the changes. Add the revised linkcard to Stage U using the instructions for adding a new linkcard (section VII.3,below).

c. If you DID NOT change the linkcard, generate it to Stage U in batch, as follows: (for screen layouts refer to item 4 ahead)

• Select option 3 - BATCH.
• Build the SCL as you do for programs.
• On the SCL generation screen, select Option 4 - GENERATE.
• On the generate screen, select copyback = Y.
• Build using map = Y.
• When done, submit the job using jobname OTXX94# & msgclass H
for (SDSF).

This process is the same as for generating (recompiling) programs; for more detail, see section VI.1.

d. Check the output in SDSF. Max down to the bottom. Verify that the module
was marked as Reentrable/Reusable with AMODE=31 and RMODE=ANY. Load modules
now reside in the appropriate Stage 1 load library. Verify that your OBJs were included and that origin of all other obj’s is correct.

e. Once you have verified that the add job ran successfully, move the link card to Stage C, using Option 4 - PACKAGE (from the Endevor Primary Options menu). This process is the same as for moving programs to Stage C; for greater detail, see sections V.7.a through f, above.

3. ADD A NEW LINKCARD

a. A new LINKCARD must be ADDED to Stage U with the correct processor
group for each system. Below is a sample processor group only! Do not assume this is the processor for your new linkcard.

---------------------------- ADD/UPDATE ELEMENTS ----------------------
OPTION ===> A

blank - Member list A - Add an element U - Update an element

TO ENDEVOR: ACTION OPTIONS:
ENVIRONMENT ===> CLAIMST CCID ===>
SYSTEM ===> ACES GENERATE ELEMENT ===> Y (Y/N)
SUBSYSTEM ===> ACES DELETE INPUT SOURCE ===> N (Y/N)
ELEMENT ===> OTXXXXXX NEW VERSION ===>
TYPE ===> LINKCARD OVERRIDE SIGNOUT ===> N (Y/N)
STAGE: U PROCESSOR GROUP ===> LEB2IL47
UPDATE IF PRESENT ===> N (Y/N)
COMMENT ===>

FROM ISPF LIBRARY: LIST OPTIONS:
PROJECT ===> OTXX94 DISPLAY LIST ===> Y (Y/N)
LIBRARY ===> LIB
TYPE ===> CNTL
MEMBER ===> OTAA2FPP THRU MEMBER ===>

FROM OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>

-------------------------------------------------------------------------

b. Submit the newly generated SCL. Check the output in SDSF. Max down to the
bottom. Verify that the module was marked as Reenterable/Reusable with
AMODE=31 and RMODE=ANY. Load modules now reside in the appropriate stage U
load library. Verify that your OBJs were included.

c. Once you have verified that the add job ran successfully, move the link card to Stage C, using Option 4 - PACKAGE (from the Endevor Primary Options menu). This process is the same as for moving programs to Stage C; for greater detail, see sections V.7.a through f, above.

Procedures on how to generate a link without changes follow on the next page.

ENDEVOR PROGRAME COMPILE

2009-08-21T21:02:00.000-07:00

PROGRAM - COMPILE
If you need to recompile a program that you haven't changed (for instance, if you changed a copybook and you want the program to pick up the new version), use Option 4 - GENERATE (from the BATCH OPTIONS MENU). Then move the element from Stage U to Stage C. FOR UPDATES TO MODULES ALL READY LOCATED IN STAGE C, SEE BELOW:

E - Endevor or 3.PP.E
4 - Claimst
3 - Batch
1 - Build SCL
4 - Generate (example follows)

1. GENERATE the element from Stage 2 or Stage C to Stage U; with COPYBACK = Y (Example below). To generate from Stage 2 you must change the “Build using map” indicator to ‘Y’.

----------------------------- GENERATE ELEMENTS -----------------------------
OPTION ===> g
ELEMENT DISPLAY OPTIONS:
blank - Element list S - Summary B - Browse H - History
G - Generate element M - Master C - Changes

FROM ENDEVOR: ACTION OPTIONS:
ENVIRONMENT ===> CLAIMS CCID ===>
SYSTEM ===> ACES COPYBACK ===> Y (Y/N)
SUBSYSTEM ===> ACES OVERRIDE SIGNOUT ===> N (Y/N)
ELEMENT ===> otxxxxxxx PROCESSOR GROUP ===>
TYPE ===> COBOL
STAGE ===> 2 1 - CLAIMS1 2 - CLAIMS2

COMMENT ===>

LIST OPTIONS:
DISPLAY LIST ===> Y (Y/N)
WHERE CCID EQ ===>
WHERE PROC GRP EQ ===>
BUILD USING MAP ===> Y (Y/N)

NOTE: Setting COPYBACK=Y does two things. It copies the Stage 2 version of the program to stage U then generates (compiles or compiles and links) it. You must still do a separate package move to put the element back into Stage C.

2. Submit the batch job. When the SCL to generate (compile) the program has been
built, PF3 back to the BATCH OPTIONS MENU. Verify that your jobcard is correct
and select option 3 to submit the job.

3. Move the Element to Stage C. This is done via the standard package
processing (see sections V.7.a through f of this document, above).

4. If the program has a linkcard associated with it:

(a) GENERATE the LINKCARD from Stage 2 or Stage C to Stage U, with COPYBACK = Y.
This is the same as the generate process for programs. (“Build using map” =
‘Y’ for Stage 2 source)

(b) MOVE the LINKCARD from Stage U to Stage C. This is also done with
package processing.

(For more information on linkcards, see section VII, below.)

5. Updating an existing module already in Stage C (test).
a. Sign out (retrieve) from Stage C - CLAIMST
b. Add element to Stage U
Generate the link (“Build using map” = ‘Y’ for Stage 2 linkcards)
d. Create a package and move the element(s) from Stage U to Stage C
e. If DB2 is used, bind using the Q panels (Wait until above completed before doing the bind - Q.14)
f. Refresh the Region (if applicable)

ENDEVOR STAGE U TO C PACKAGE

2009-08-21T21:01:00.000-07:00

Submit your Stage U to Stage C Package
---------------------- Package Foreground Options Menu ------------------------
Option ===> 5

1 DISPLAY - Display Package Information
2 CREATE/MODIFY - Create or Modify Package
3 CAST - Prepare Package for Review
4 REVIEW - Approve or Deny Package
5 EXECUTE - Submit or Execute Package
6 SHIP - Ship Packages
7 BACKOUT - Perform Backout or Backin Processing
8 COMMIT - Clear Backout Information
9 UTILITIES - Reset, Delete, or Export Package
L DistribuLink - Perform Product Collection Request

Package ID ===> OTDH94060899A

Limit selection list by Package Status. These are used by the DISPLAY
and UTILITIES options:

In-Edit......... Y In-Execution.... Y
In-Approval..... Y Executed........ Y
Denied.......... Y Committed....... Y
Approved........ Y

for submit pkg screen print……………

10. After the package batch job runs successfully (return code 00 or 04):
a. check STAGE U libraries, verifying that all related members (load modules, DBRMs) were deleted.

b. check the Stage C libraries and verify the changes. The element(s) should
reflect the current date and the DBRM should have the user id used when the
job was submitted. See library document for the library dataset names.

c. Review dataset: IMSVSH.PROCLIB(DFSMPLT7) to see if your program is
preloaded. If it is, you need to refresh the region.
(If someone enters into the screen prior to you completing this step,
they will abend, but the abend will automatically refresh the region).

Refresh the Region:
ISPF Primary Option Menu
Option ===> V.I (to enter Boole & Babbage)
More: +
0 Settings Terminal and user parameters User ID . : OTDH94
1 View Display source data or listings Time. . . : 10:08
2 Edit Create or change source data Terminal. : 3278
3 Utilities Perform utility functions Screen. . : 1
4 Foreground Interactive language processing Language. : ENGLISH
5 Batch Submit job for language processing Appl ID . : ISR
6 Command Enter TSO or Workstation commands TSO logon : QWIKC
7 Dialog Test Perform dialog testing TSO prefix: OTDH94
8 PROD UPDATES Perform production control updates System ID : SYSC
11 Workplace ISPF Object/Action Workplace MVS acct. : TSO00XXX
I INFO Information Management Release . : ISPF 4.4
C CHANGES Display summary of changes
E ENDEVOR ENDEVOR Processing
M VPS 6.1 Local Printing through VPS
O OTC Toolbox OTC Toolbox Main Menu - CASA
P PANVALET Panvalet
Q ACES ACES Tool Box

Enter X to Terminate using log/list defaults

Boole & Babbage ------------ IMS OPERATOR WORKSTATION ------------ AutoOPERATOR
OPTION ===> 6 DATE -- 99/06/10
TIME -- 10:10:04
USERID -- OTDH94
1 STATUS - DISPLAY STATUS OF AN IMS SYSTEM MODE -- ISPF 4.4
2 NETWORK - DISPLAY/MODIFY LINE/TERM/NODE
3 DATABASE - DISPLAY/MODIFY DATABASE
4 TRANSACTION - DISPLAY/MODIFY TRANCODE
5 PROGRAM - DISPLAY/MODIFY PROGRAM
6 REGIONS - DISPLAY/MODIFY IMS REGION
PF1/13: HELP
X EXIT - TERMINATE PF3/15: EXIT

BOOLE AND BABBAGE ------------------ REGIONS ------------------- AutoOPERATOR
COMMAND ===> /sta reg imsotc1t ***enter*** TGT ===> IMSH
#MPPS>> 17/ 1 #QUEUED>> 3 MQC1>> CONNECTED/ 14/ 6 INTVL===> 3
#BMPS>> 2 #QUEUED>> 0 DB2T>> CONNECTED/ 13/ 8 STATUS--- INPUT
#IFPS>> 0 #QUEUED>> 0 DATE----- 99/06/10
#DBTS>> 2/ 0 TIME----- 10:11:22
LC CMDS: P(STOP), A(ABDUMP), C(CANCEL), PW(STOP WFI)
LC JOBNAME TYP TRANCODE PSBNAME LTERM CLS RGN WKSET # SIOS CPU TIME
IMSPM1T MPP 1 500K 25,493 18.93
IMSPM1X MPP 2 1596K 4,747 1.33
IMSWB1X MPP 3 624K 2,996 .93
IMSBM1X MPP 4 276K 2,076 .52
IMSWB1T MPP 5 292K 2,330 .75
IMSMP1T MPP 6 308K 638 .16
IMSOTC1X MPP 8 272K 1,171 .28
IMSPM1Z MPP 9 228K 341 .17
IMSMQ1T MPP 10 500K 4,955 4.89
SYIM86MH BMP CSQQTRMN 11 284K 150 3.74
IMSPRODH MPP 12 260K 1,886 .90
IMSOTC1T MPP 13 2044K 12,372 4.19
TPCICSCT DBT 14 4996K 13,913 24.72
IMSWB2X MPP 16 948K 5,223 1.96
IMSWB2T MPP 17 668K 2,503 .85
IMSMP1X MPP 19 380K 17,655 18.37

YOU WILL SEE THAT ONE IS EXECUTING AND ONE IS WAITING (OR SEVERAL)

- Enter after keying in the /sta command
- Type a P (purge) at the region you want to stop and get refreshed
- Hit enter a few times - you should see IMSOTC1T disappear and then reappear
(when this is done, personnel in the online system clock until it’s completed)

11. Table Edit Programs

- Perform normal steps for modifying a program beginning with Endevor Retrieve
as outlined in section V. Program Updates.

- A specific processor group is assigned to the table edit programs. It will create a load member in PROD.TB.END.STAGE.IMSLOAD.

- PROD.TB.END.STAGE.IMSLOAD is copied to system A, PROD.TB.END.IMSLOAD,
nightly.

ENDEVOR CAST

2009-08-21T21:00:00.000-07:00

CAST (Example below).

PACKAGE ------------------ PACKAGE OPTIONS MENU -----------------------------
OPTION ===> 3

1 DISPLAY - Display Package Information
2 CREATE/MODIFY - Create or Modify Package
3 CAST - Prepare Package for Review
4 REVIEW - Approve or Deny Package
5 EXECUTE - Submit or Execute Package
6 SHIP - Ship Packages
7 BACKOUT - Perform Backout or Backin Processing
8 COMMIT - Clear Backout Information
9 UTILITIES - Reset, Delete, or Export Package

PACKAGE ID ===> OTXX94030294A

LIMIT SELECTION LIST BY PACKAGE STATUS: (Y/N - Options 1 & 9)

In-Edit......... Y In-Execution.... Y
In-Approval..... Y Executed........ Y
Denied.......... Y Committed....... Y
Approved........ Y

----------------------------------------------------------------------------

7f. Select C - Cast Package (Example below).

--------------------------------------------------------------------------------

CAST ------------------------- CAST PACKAGE ---------------------------------
OPTION ===> c

C - Cast Package S - Display SCL

PACKAGE ID: OTXX94030294A STATUS: IN-EDIT
DESCRIPTION: MOVE PROGRAM UPDATES TO PRODUCTION
PACKAGE TYPE: STANDARD
SHARABLE PACKAGE: N
VALIDATE COMPONENTS ===> N (Y/N/W)
ENABLE BACKOUT ===> Y (Y/N)
EXECUTION WINDOW FROM ===> 02MAR94 00:00 TO ===> 31DEC99 00:00

USER ID DATE TIME
CREATED: OTXX94 02MAR94 13:24
LAST UPDATED:
---------------------------------------------------------------------------
After you have cast the package, the system returns to the PACKAGE OPTIONS MENU, where the message "CAST SUCCESSFUL" is displayed in the upper-right corner.

At this point, you need to review/approve, execute/submit your job (15 Claimst approvers in ACES). This job executes the package and moves the program to production. It is jobname MAENDVR and will be in $AVRS on system C.
8. Approve your Stage U to Stage C package
---------------------- Package Foreground Options Menu ------------------------
Option ===> 4

1 DISPLAY - Display Package Information
2 CREATE/MODIFY - Create or Modify Package
3 CAST - Prepare Package for Review
4 REVIEW - Approve or Deny Package
5 EXECUTE - Submit or Execute Package
6 SHIP - Ship Packages
7 BACKOUT - Perform Backout or Backin Processing
8 COMMIT - Clear Backout Information
9 UTILITIES - Reset, Delete, or Export Package
L DistribuLink - Perform Product Collection Request

Package ID ===> OTDH94060899A (Your id, today’s date, unique letter)

Limit selection list by Package Status. These are used by the DISPLAY
and UTILITIES options:

In-Edit......... Y In-Execution.... Y
In-Approval..... Y Executed........ Y
Denied.......... Y Committed....... Y
Approved........ Y

for approve screen print……………

ENDEVOR MOVE OPTION

2009-08-21T20:58:00.000-07:00

MOVE (Example below).
------------------------------- SCL GENERATION ------------------------------
OPTION ===> 5

1 DISPLAY - Display an element
2 ADD/UPDATE - Add or update an element into stage 1
3 RETRIEVE - Retrieve or copy an element
4 GENERATE - Execute the Generate Processor for this element
5 MOVE - Move an element to the next inventory location
6 DELETE - Delete an element
7 PRINT ELEMENT - Print elements, changes and detail change history
8 SIGNIN - Explicitly sign-in an element
9 TRANSFER - Transfer elements between two ENDEVOR locations
10 PRINT MEMBER - Print a compressed listing or member
11 LIST ELEMENT - Create List actions for ENDEVOR elements
12 LIST MEMBER - Create List actions for external members
13 ARCHIVE - Archive elements

REQUEST DATA SET: PACKAGE - OTXX94030294A
APPEND: N
-------------------------------------------------------------------------------

7d. Option O - Move Element (Example below).

------------------------------- MOVE ELEMENTS -------------------------------
OPTION ===> o
ELEMENT DISPLAY OPTIONS:
blank - Element list S - Summary B - Browse H - History
O - Move element M - Master C - Changes

FROM ENDEVOR: ACTION OPTIONS:
ENVIRONMENT ===> CLAIMST CCID ===>
SYSTEM ===> ACES SYNC ===> N (Y/N)
SUBSYSTEM ===> ACES WITH HISTORY ===> N (Y/N)
ELEMENT ===> othirpt1 RETAIN SIGNOUT ===> N (Y/N)
TYPE ===> COBOL SIGNOUT TO ===>
STAGE ===> U ACKNOWLEDGE ELM JUMP ===> N (Y/N)
U - CLAIMSU C - CLAIMSC DELETE 'FROM' ELEMENT ===>Y (Y/N)

COMMENT ===>
LIST OPTIONS:
DISPLAY LIST ===> Y (Y/N)
WHERE CCID EQ ===>
WHERE PROC GRP EQ ===>
BUILD USING MAP ===> N (Y/N)
-------------------------------------------------------------------------------
You may continue to fill in this screen and hit enter for each element to be moved; OR you may leave the element name and type blank, keep DISPLAY LIST=Y and get an element selection list. Put an 'o' next to each element you wish to move in your package. This option builds many SCL statements at once. Make sure “BUILD USING MAP = N” or you will be waiting for a while.

When finished building the package, PF3 to the SCL GENERATION SCREEN. Note that in the upper right hand corner of this screen a message displays "# REQUEST(S) BUILT". This message verifies that the SCL to move the element(s) was built.

PF3 again to the CREATE/MODIFY PACKAGE screen; the upper right hand corner displays
the message "PACKAGE CONSTRUCTED". Then PF3 once more to the PACKAGE OPTIONS MENU.

CREATING A PACKAGE FROM ENDEVOR PRIMARY OPTIONS MENU

2009-08-21T20:50:00.000-07:00

Create a PACKAGE, from the Endevor Primary Options Menu; select:

Option 4 - PACKAGE
Option 2 - CREATE/MODIFY (Example below).

PACKAGE ------------------ PACKAGE OPTIONS MENU -----------------------------
OPTION ===> 2

1 DISPLAY - Display Package Information
2 CREATE/MODIFY - Create or Modify Package
3 CAST - Prepare Package for Review
4 REVIEW - Approve or Deny Package
5 EXECUTE - Submit or Execute Package
6 SHIP - Ship Packages
7 BACKOUT - Perform Backout or Backin Processing
8 COMMIT - Clear Backout Information
9 UTILITIES - Reset, Delete, or Export Package

PACKAGE ID ===> otxx94030294a

LIMIT SELECTION LIST BY PACKAGE STATUS: (Y/N - Options 1 & 9)

In-Edit......... Y In-Execution.... Y
In-Approval..... Y Executed........ Y
Denied.......... Y Committed....... Y
Approved........ Y

NOTE: The PACKAGE ID should be your 6 position TSO ID, today's date (MMDDYY) and a 1 position sequence letter.

Option B - Build Package Actions (Example below).
-----------------------------------------------------------------------------
MODIFY ------------------- CREATE/MODIFY PACKAGE ----------------------------
OPTION ===> b

B - Build Package Actions I - Import SCL
E - Edit Package C - Copy Package

PACKAGE ID: OTXX94030294A STATUS: IN-EDIT
DESCRIPTION ===> move program updates to Stage C
PACKAGE TYPE ===> STANDARD
SHARABLE PACKAGE ===> N (Y/N) APPEND TO PACKAGE ===> N (Y/N)
ENABLE BACKOUT ===> Y (Y/N)
EXECUTION WINDOW FROM ===> 02MAR94 00:00 TO ===> 31DEC99 00:00

INPUT PACKAGE ID ===>

FROM ISPF LIBRARY:
PROJECT ===> OTXX94
GROUP ===> LIB
TYPE ===> CNTL
MEMBER ===>

OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>

NOTE: A DESCRIPTION is required.

ENDEVOR ACTIONS SUBMITING SCL

2009-08-21T20:48:00.001-07:00

Submit SCL (Example below).
BATCH ----------------------- BATCH OPTIONS MENU ----------------------------
OPTION ===> 3

1 BUILD SCL - Build batch SCL actions
2 EDIT - Edit request data set
3 SUBMIT - Submit job for batch processing
4 VALIDATE - Check request data set for syntax errors
5 BUILD JCL - Enter additional JCL to be included with the job

REQUEST DATA SET:
PROJECT ===> OTLD94 APPEND ===> N (Y/N)
GROUP ===> ENDEVOR INCLUDE JCL ===> N (Y/N)
TYPE ===> SCL
MEMBER ===> PGMADD

OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DSNAME ===>

JOB STATEMENT INFORMATION:
===> //OTXX94# JOB (44001,FS01,00000,1111),'PROJECT C583', => PROJECT NAME
===> // CLASS=A,MSGCLASS=H,NOTIFY=OT???? => YOUR ID
===> //*
===> //*$AVRS C=OTCACTSD =>(comment what program/linkcard/binddeck/sysin)

NOTE: Make sure the project code in the jobcard is correct. Use Class = A if there are many elements involved.
----------------------------------------------------------------------------------
Select Option 3 to submit the job. This job:

(a) creates a compiled listing;
(b) creates a load module in the appropriate stage U load library or object code in the appropriate stage U object library;
(c) for DB2 programs, creates the DBRM member in the appropriate stage U dbrm library.
• When done, submit the job using jobname OTXX94# & msgclass H (SDSF).

6. Check Stage U libraries for your updated module (can’t move to Stage C if your
not in Stage U). See library document for library dataset names.

7. MOVE - From Stage U to Stage C (Test).

After a successful add, update or generate (for type LINKCARD) to Stage U, a MOVE is done from STAGE U to STAGE C.

You should do all your MOVES in one package (after the ADDS, UPDATES or GENERATES have executed successfully), however, when the package executes, the MOVES will not necessarily be executed in the order that you built the SCL.
The objective of the mapped environment is to use one package for the entire process so this package should contain all elements needed for production. Remember the package name for implementation purposes.

The current ELEMENT TYPE Sequence Processing order for processing packages is available for viewing (listed below) or by going to ENDEVOR panel E;4;1;7 (DISPLAY TYPE). In the ENVIRONMENT ===> field enter 'CLAIMST', leave the SYSTEM ===> field blank, and the TYPE ===> field blank, select the STAGE ===> you wish to view . This will bring up a list of all available systems. Select the desired system by tabbing down to the left of the desired system place a 'S' there and . This will display the current order in which elements will be processed in the package.

ORDER OF OPERATIONS:
--------------------------- TYPE SELECTION LIST ------------ Row 1 to 9 of 9
COMMAND ===> SCROLL ===> CSR

CURRENT ENV: CLAIMST STAGE ID: U SYSTEM: ACES
NEXT ENV: CLAIMST STAGE ID: C SYSTEM: ACES

TYPE TYPE DESCRIPTION
MFS ACES MFS
BINDDECK ACES LINK BIND CONTROL STATEMENTS
LINKCARD ACES LINK CONTROL STATEMENTS
COPYBOOK ACES COPYBOOKS
PROC ACES JCL PROCEDURES
UTL ACES CONTROL CARDS/JOBSYSIN
ASSM ACES ASSEMBLER PROGRAMS
COBOL ACES COBOL PROGRAMS
TELON ACES TELON PROGRAMS
******************************* Bottom of data ********************************

ENDEVOR ACTIONS

2009-08-21T20:48:00.000-07:00

ENDEVOR PROCESSOR GROUPS

2009-08-21T20:47:00.000-07:00

5f. Viewing a List of Processor Groups:
E - ENDEVOR/MVS Environment Selection
4 - CLAIMST
1 - DISPLAY
8 - PROCESSOR GROUP
Fill out the Environment, System, Type, and Stage. Put a * in the Group…

The available choices to date are:

ACES: Stage U
--------------------- PROCESSOR GROUP SELECTION LIST ------- Row 1 to 5 of 5
COMMAND ===> SCROLL ===> CSR

CURRENT ENV: CLAIMST STAGE ID: U SYSTEM: ACES TYPE: TELON
NEXT ENV: CLAIMST STAGE ID: C SYSTEM: ACES TYPE: TELON

PROCESSOR
GROUP PROCESSOR GROUP DESCRIPTION
*NOPROC* DEFAULT PROCESSOR -- NO COMPILE
CMVNIL47 ONLINE TELON 2.4 COB/MVS TABLE SYSTEM LOAD LIBRARY
CMVNIODD ONLINE TELON 2.4 COB/MVS STATIC OBJECT DRIVER PGMS (Telon Drivers)
CMVNIODS ONLINE TELON 2.4 COB/MVS STATIC OBJECT SUB PROGRAM (Telon subprograms
w/DB2)
CMV2IODS ONLINE TELON 2.4 COB/MVS DB2 STATIC OBJ SUB PROGRM (Telon subprograms
w/out DB2)
******************************* Bottom of data ********************************

LEB2IL47 ONLINE TELON 2.4 COB/MVS LINK WITH DB2

LEBNIL47 ONLINE TELON 2.4 COB/MVS LINK WITHOUT DB2

ACES: Stage C
--------------------- PROCESSOR GROUP SELECTION LIST ------- Row 1 to 4 of 4
COMMAND ===> SCROLL ===> CSR

CURRENT ENV: CLAIMST STAGE ID: C SYSTEM: ACES TYPE: TELON
NEXT ENV: CLAIMS STAGE ID: 2 SYSTEM: ACES TYPE: TELON

PROCESSOR
GROUP PROCESSOR GROUP DESCRIPTION
*NOPROC* DEFAULT PROCESSOR -- NO COMPILE
CMVNIODD ONLINE TELON 2.4 COB/MVS STATIC OBJECT DRIVER PGMS (Telon Drivers)
CMVNIODS ONLINE TELON 2.4 COB/MVS STATIC OBJECT SUB PROGRAM (Telon subprograms
w/DB2)
CMV2IODS ONLINE TELON 2.4 COB/MVS DB2 STATIC OBJ SUB PROGRM (Telon subprograms
w/out DB2)
******************************* Bottom of data ********************************

LEB2IL47 ONLINE TELON 2.4 COB/MVS LINK WITH DB2

LEBNIL47 ONLINE TELON 2.4 COB/MVS LINK WITHOUT DB2

ALF:

COBOL Stage 1:
CIINBL48 - COBOLII BATCH PROCESSOR AMODE31
CIINBOD8 - COBOLII OBJECT MODULES
CII2BL48 - COBOLII DB2 BATCH PROCESSOR AMODE31

TELON Stage 1:

CIA2BOD8 COBOLII/DB2 TELON 2.4 SUB PROGRAM OBJECT MODULE
CIENBOD8 COBII TELON 2.4 BASE SUB PROGRAM OBJECT MODULE
CIFNBOD8 COBII TELON 2.4 BASE DRIVER PROGRAM OBJECT MODULE
COBNBLB0 COBOLII TELON 2.4 BATCH PROCESSOR AMODE31

If a new program has been created that does not fit into one of these groups, then a NEW Processor Group will have to be defined.

ENDEVOR ADD/UPDATE

2009-08-21T20:44:00.000-07:00

5d. OPTION 2 - ADD/UPDATE (Example Continued).

---------------------------- ADD/UPDATE ELEMENTS ----------------------------
OPTION ===> a

blank - Member list A - Add an element U - Update an element

TO ENDEVOR: ACTION OPTIONS:
ENVIRONMENT ===> CLAIMST CCID ===>
SYSTEM ===> ACES GENERATE ELEMENT ===> Y (Y/N)
SUBSYSTEM ===> ACES DELETE INPUT SOURCE ===> N (Y/N)
ELEMENT ===> othirpt1 NEW VERSION ===>
TYPE ===> COBOL OVERRIDE SIGNOUT ===> N (Y/N)
STAGE: U PROCESSOR GROUP ===>
COMMENT ===> brief explaination UPDATE IF PRESENT ===> N (Y/N)
of change
FROM ISPF LIBRARY: LIST OPTIONS:
PROJECT ===> OTXX94 DISPLAY LIST ===> Y (Y/N)
LIBRARY ===> END
TYPE ===> SOURCE
MEMBER ===> othirpt1 THRU MEMBER ===>

FROM OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>

NOTE: If the element is being added to Endevor for the first time, you must specify the PROCESSOR GROUP for Endevor to use. See list of appropriate processor groups.
---------------------------------------------------------------------------------

After you have typed in all the information needed on the ADD/UPDATE screen,
PF3 to the SCL GENERATION screen. Note that in the upper right hand corner of this
screen a message reads "1 REQUEST(S) BUILT". This message verifies that the ADD/UPDATE of the element was built into the SCL data set and is ready to
submit as a batch job.

From the SCL GENERATION screen, PF3 to the BATCH OPTIONS MENU screen.

5e. Processor Group Notes

If the program existed in Endevor, a Processor Group has been assigned. Leave the PROCESSOR GROUP (under ACTION OPTIONS) blank, as in the above example. Endevor uses the existing Processor Group.

If you are adding DB2 to an existing program or adding a program for the first time - a NEW Processor Group needs to be assigned to the program. To assign a Processor Group, on the ADD/UPDATE ELEMENTS screen: type one of the existing processor groups in, or place "*" on the PROCESSOR GROUP option. When you type an asterisk, Endevor displays the entire list of Processors for the type indicated (COBOL, TELON, PL1 or ASSM). Place an "S" next to the appropriate processor and hit enter. The following shows an example of the display for processor group selection.

ENDEVOR PROGRAM UPDATES

2009-08-21T20:41:00.001-07:00

b. Retrieve the program to yourid.LIB.SOURCE.

c. If two or more people are changing the same program, the second person can get
a copy of the existing production version by retrieving it from Endevor but
changing SIGNOUT ELEMENT (under ACTION OPTIONS) from "Y" to "N". The second
person should retrieve it to a PDS other than yourid.LIB.SOURCE. This kind of
retrieval makes a copy of the program but it is still signed out to the first
person.

d. If the second person must put in his/her change before the first person, an
approver can override the original signout. The approver perfroms the ADD
action to put second person's version to Stage U by changing OVERRIDE SIGNOUT
(under ACTION OPTIONS) from "N" to "Y".

4. Apply the program revisions to the element in yourid.LIB.SOURCE (or library of
your choice).

5. ADD - From External PDS to CLAIMST Stage U.

5a. ADD the program into Stage U through the BATCH option.

E - ENDEVOR or 3.PP.E
4 - CLAIMST
3 - BATCH
1 - BUILD SCL (Example Follows)
2 - ADD/UPDATE (Example Follows)
3 - Submit SCL (Example Follows)

5b. Option 1 - BUILD SCL (Example below).

BATCH ----------------------- BATCH OPTIONS MENU ----------------------------
OPTION ===> 1

1 BUILD SCL - Build batch SCL actions
2 EDIT - Edit request data set
3 SUBMIT - Submit job for batch processing
4 VALIDATE - Check request data set for syntax errors
5 BUILD JCL - Enter additional JCL to be included with the job

REQUEST DATA SET:
PROJECT ===> Your Library APPEND ===> N (Y/N)
GROUP ===> ENDEVOR INCLUDE JCL ===> N (Y/N)
TYPE ===> SCL
MEMBER ===> PGMADD

OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DSNAME ===>

EXAMPLE OF THE JOB STATEMENT INFORMATION ON THE NEXT PAGE…
JOB STATEMENT INFORMATION:
===> //OTXX94# JOB (44001,FS01,00000,1111),'PROJECT C583', => PROJECT NAME
===> // CLASS=A,MSGCLASS=J,NOTIFY=OT???? => YOUR ID
===> //*
===> //*$AVRS C=OTCACTSD =>(comment what program/linkcard/binddeck/sysin)

5c. OPTION 2 - ADD/UPDATE (Example below).

------------------------------- SCL GENERATION ---------- 0 REQUEST(S) BUILT
OPTION ===> 2

1 DISPLAY - Display an element
2 ADD/UPDATE - Add or update an element into stage U
3 RETRIEVE - Retrieve or copy an element
4 GENERATE - Execute the Generate Processor for this element
5 MOVE - Move an element to the next inventory location
6 DELETE - Delete an element
7 PRINT ELEMENT - Print elements, changes and detail change history
8 SIGNIN - Explicitly sign-in an element
9 TRANSFER - Transfer elements between two ENDEVOR locations
10 PRINT MEMBER - Print a compressed listing or member
11 LIST ELEMENT - Create List actions for ENDEVOR elements
12 LIST MEMBER - Create List actions for external members
13 ARCHIVE - Archive elements

REQUEST DATA SET: OTXX94.LIB.CNTL(TEMP)
APPEND: N

ENDEVOR PROGRAM UPDATES

2009-08-21T20:41:00.000-07:00

ENDEVOR PROGRAM UPDATES

2009-08-21T20:39:00.000-07:00

PROGRAM UPDATES

If the program is an Audatex program (OTMISCED, OT51B10, OT52B10, OT54B10), see section XV.

The following paragraphs outline the steps involved from signing out a program to signing it back in.

1. Sign out your module (copybook, program, proc etc…) by listing your modules in the implementation checklist either for that months implementation or at the bottom under “ON-GOING DEVELOPMENT EFFORT : SIGNED OUT ELEMENTS :”

2. Look at PAL INFO\Admin\ENDEVOR\CHGNOTFY.XLS. There are several other groups that

must be notified if we make changes in ACES to certain designated programs. The

SCREEN CHANGE NOTIFICATION EXCEL Spreadsheet will identify the programs, that if

changed, will impact other groups, and who should be notified. The Project

Leader should contact these other groups at the very beginning of the project to

ensure that they have the appropriate time needed to make any necessary changes.

3. RETRIEVE - From Endevor Stage 2 (Production) To yourid.LIB.SOURCE (or the library

of your choice).

a. If an element exists in Endevor, a "RETRIEVAL" (through FOREGROUND Option)

must done first. The person "signing out" the element is then responsible

for placing it back into Endevor. Select the following options from the TSO

Primary Menu:

E - ENDEVOR or 3.PP.E

5 - CLAIMS

2 - FOREGROUND

3 - RETRIEVE (Example below:)

----------------------------- RETRIEVE ELEMENTS -----------------------------

OPTION ===> r

ELEMENT DISPLAY OPTIONS:

blank - Element list S - Summary B - Browse H - History

R - Retrieve element M - Master C - Changes

FROM ENDEVOR: ACTION OPTIONS:

ENVIRONMENT ===> CLAIMS CCID ===>

SYSTEM ===> ACES EXPAND INCLUDES ===> N (Y/N)

SUBSYSTEM ===> ACES SIGNOUT ELEMENT ===> N (Y/N)

ELEMENT ===> othirpt1 OVERRIDE SIGNOUT ===> N (Y/N)

TYPE ===> COBOL REPLACE MEMBER ===> N (Y/N)

STAGE ===> 2 1 - CLAIMS1 2 - CLAIMS2

COMMENT ===> update per request

TO ISPF LIBRARY: LIST OPTIONS:

PROJECT ===> otxx94 DISPLAY LIST ===> Y (Y/N)

LIBRARY ===> end WHERE CCID EQ ===>

TYPE ===> source WHERE PROC GRP EQ ===>

MEMBER ===> othirpt1 BUILD USING MAP ===> N (Y/N)

FIRST FOUND ===> Y (Y/N)

TO OTHER PARTITIONED OR SEQUENTIAL DATA SET:

DATA SET NAME ===>

-----------------------------------------------------------------------------------

ENDEVOR OPERATION/ACTION

2009-08-21T20:38:00.000-07:00

II. GENERAL ORDER OF ENDEVOR OPERATION/ACTION

Endevor actions are generally performed in the following order:

RETRIEVE - also signs element out to retriever (refer to section V for more detail)

ADD/UPDATE - executes generate processor for program, creates obj and/or dbrm

and/or load module (refer to section V for more detail); simply adds

element if generate processor is *NOPROC*

*NOPROC* = PROCS, UTLS, BINDDECKS, COPYBOOKS, AND MFS

(NOPROC doesn’t mean no processing. It means that it’s added to

Stage U datasets without any action taking place on the element,

it’s an “as is” move…

GENERATE - executes generate processor for:

Type = Telon, then a compile will take place or

Type = Cobol, then a compile and possibly a link will take place

Type = Linkcard, then a link will take place

- Create either an obj, obj & load module, or just a load module

(refer to sections VI and VII for more detail)

******** - VERIFY STAGE U LIBRARIES

MOVE - executes move and delete processors

- copies from Stage U to Stage C libraries

- deletes from Stage U; signs element back in to Stage C

(refer to section V.7 for more detail)

******** - VERIFY STAGE C LIBRARIES

EXTERNAL TO ENDEVOR - copy jobs execute to copy dbrms and load modules to production libraries; bind job executes; deletes from Stage C

ENDEVOR ACTIONS

2009-08-21T20:36:00.000-07:00

The following are generally the Endevor actions that you will use:

RETRIEVE - execute in foreground to retrieve element(s) from Stage 2 to your external PDS.

ADD/UPDATE - execute in batch to add element to Stage U or update it if it is already in Stage U.

GENERATE - generate always executes when you add (or update) a program to Stage U; you also explicitly use generate when relinking.

MOVE - you must use the functions in a package to get an element and its associated outputs (objs, dbrms, loads) to Stage C.

DELETE - you may use delete to remove an element from Stage U or C.

SIGNIN - if you have inadvertently signed a member out, you must use a package and specify override signout=Y to sign it back in to Stage C.

PRACTICAL QUESTIONS (JCL)

2009-08-21T20:35:00.000-07:00

1. Create a PDS and 5 Memebers
2. Create a PS and 5 members
3. Write COBOL program for Addtion of 2 numbers (ADDPRG)
4. Write COBOL program for subtraction of 2 numbers (SUB PRG)
5. Write COBOL program for multiplication of 2 numbers (MULPRG)
6. Write COBOL program for division of 2 numbers (DIVPRG)
7. Write a JCL program to excute ADDPRG using DD *
8. Write a JCL program to excute ADDPRG using DD Dummy..
9. Write a JCL program to excute ADDPRG,SUBPRG,MULPRG and DIVPRG.
10. Write a JCL prgram to set TIME for above program and watch.
11. Write a JCL program to create a PS
12. Write a JCL program to create a PDS.
13. Write a JCL catalog procedure for ADDPRG and call it from other JCL program.
14. Write a JCL instream procedure for ADDPRG and call it.
15. Write a JCL procedure with Symbolic Parameter.
16. Write a JCL procedure with Overriding Parameter
17. Write a COBOL Program to copy records from one file to other file.
18. Write a JCL program to copy data from PS to PS using IEBGENER.
19. Write a JCL program to copy all data from PDS to PDS using IEBCOPY.
20. Write a JCL program to copy selected data from PDS to PDS using IEBCOPY.
21. Write a JCL program to copy other than selected data from PDS to PDS using IEBCOPY.
22. Write a JCL program to print all data from PS using IEBPTPCH
23. Write a JCL program to Rename a Dataset using IEHPROGM
24. Write a JCL program to Delete a Dataset using IEHPROGM
25. Write a JCL program to Catalog a Dataset using IEHPROGM
26. Write a JCL program to Un-Catalog a Dataset using IEHPROGM
27. Write a JCL program to sort records in Ascending order using SORT
28. Write a JCL program to sort records in Descending order using SORT
29. Write a JCL program to sort records with atleast 2 fields order using SORT

JCL QUESTIONS

2009-08-21T20:33:00.000-07:00

1. What is the difference between DD * , DD Data and DUMMY statement.

2. What is DLM? Can we use // or /* in DLM statement?

3. What is meant by DSN?

4. What is DISP? What are its parameters? (D1,D2.D3)

5. Explain about NEW, OLD, SHR and MOD.

6. Explain about KEEP, DELETE, PASS, CATLG and UNCATLG.

7. Explain about third parameter in DISP Parameter. (D3)

8. What is UNIT ? Explain its parameters.

9. What is VOL? Explain its parameters

10. What is LABEL Parameters?

11. What is SPACE Parameters?

12. What is Load Data Set?

13. What is JOBLIB?

14. What is STEPLIB?

15. What is the difference between JOBLIB and STEPLIB?

16. What is SYSIN and SYSOUT?

17. What is OCB. Explain its 5 parameters

18. What is LRECL. Explain it with COBOL statement.

19. What is BLKSIZE. Explain it with COBOL statement.

20. What is RECFM. Explain it with COBOL statement.

21. What is DSORG. Explain it with COBOL statement.

22. What is EROPT. Explain it with COBOL statement.

23. What is V, F, U, VB, VF, VBA and FBA?

24. What is PROCEDURE? What are its 2 types?

25. What is Instream procedure?

26. What is catalog procedure?

27. Explain the coding rules for a Procedure? (4 points)

28. Explain the coding rules for a Instream Procedure.(4 points)

29. What is IIP, DIP, ICP, DCP and IAP?

30. How many types of Parameters are in Procedure.

31. What is Symbolic Parameters?

32. What is Overriding Parameter?

33. Explain filecopy method in Mainframe

34. What is meant by JCL Utilities?

35. What are the rules for JCL Utilities?

36. What is IEBGENER?

37. What is IEBCOPY?

38. What is IEBPTPCH?

39. How do u copy all members from one DSN to other DSN?

40. How do u copy a particular members from one DSN to other DSN?

41. How do u copy other than selected members from one DSN to other DSN?

42. What is meant by System Utilities?

43. What is IEHPROGM?

44. What are the rules for System Utilities?

45. Explain RENAME, NEWNAME, UNCATLG, CATLG and DELETE

46. What are the differece between System Utilities and JCL Utilities

47. Explain about Other Utilities?

48. Explain SORT Utility

49. Explain SORT FIELDS parameter.

50. Explain if SORT Parameter CH has the value BI or X or PD or ZD or AC or CH.

jcl questions

2009-08-21T20:31:00.000-07:00

1. What is DLM? Can we use // or /* in DLM statement?

2. What is meant by DSN?

3. What is DISP? What are its parameters? (D1,D2.D3)

4. Explain about NEW, OLD, SHR and MOD.

5. Explain about KEEP, DELETE, PASS, CATLG and UNCATLG.

6. Explain about third parameter in DISP Parameter. (D3)

7. What is UNIT ? Explain its parameters.

8. What is VOL? Explain its parameters

9. What is LABEL Parameters?

10. What is SPACE Parameters?

11. What is Load Data Set?

12. What is JOBLIB?

13. What is STEPLIB?

14. What is the difference between JOBLIB and STEPLIB?

15. What is SYSIN and SYSOUT?

16. What is OCB. Explain its 5 parameters

17. What is LRECL. Explain it with COBOL statement.

18. What is BLKSIZE. Explain it with COBOL statement.

19. What is RECFM. Explain it with COBOL statement.

20. What is DSORG. Explain it with COBOL statement.

21. What is EROPT. Explain it with COBOL statement.

22. What is V, F, U, VB, VF, VBA and FBA?

23. What is PROCEDURE? What are its 2 types?

24. What is Instream procedure?

25. What is catalog procedure?

26. Explain the coding rules for a Procedure? (4 points)

27. Explain the coding rules for a Instream Procedure.(4 points)

28. What is IIP, DIP, ICP, DCP and IAP?

29. How many types of Parameters are in Procedure.

30. What is Symbolic Parameters?

31. What is Overriding Parameter?

32. Explain filecopy method in Mainframe

33. What is meant by JCL Utilities?

34. What are the rules for JCL Utilities?

35. What is IEBGENER?

36. What is IEBCOPY?

37. What is IEBPTPCH?

38. How do u copy all members from one DSN to other DSN?

39. How do u copy a particular members from one DSN to other DSN?

40. How do u copy other than selected members from one DSN to other DSN?

41. What is meant by System Utilities?

42. What is IEHPROGM?

43. What are the rules for System Utilities?

44. Explain RENAME, NEWNAME, UNCATLG, CATLG and DELETE

45. What are the differece between System Utilities and JCL Utilities

46. Explain about Other Utilities?

47. Explain SORT Utility

48. Explain SORT FIELDS parameter.

49. Explain if SORT Parameter CH has the value BI or X or PD or ZD or AC or CH.

JCL QUESTIONS

2009-08-21T20:28:00.000-07:00

1. What is JCL?
2. Difference between JCL and COBOL-II
3. What is JOB?
4. What is PROC?
5. What are the difference between JOB and PROC?
6. List all JCL statements
7. What is EXEC statement?
8. What is DD statement?
9. What is meant by // and /* and //*
10. What is PROC and PEND statement?
11. What is OUTPUT statement?
12. How many EXEC statement allowed in a single JCL? (255)
13. How many DD statement allowed in a single JCL? (3273)
14. Explain JCL coding format
15. What is Parameter? Tell its 2 types.
16. What is POSITIONAL PARAMETER?
17. What is KEYWORD PARAMETER?
18. What is JOBNAMEs? Explain its rules.
19. What is 2 parts of POSITIONAL PARAMETER?
20. Explain Accounting Information in POSITIONAL PARAMETER
21. Explain Programmer Information in POSITIONAL PARAMETER
22. What is KEYWORD PARAMETER? How do u find it ? (By = sign)
23. What is CLASS Parameter?
24. What is PRTY Parameter?
25. What is MSGCLASS Parameter?
26. What is MSGLEVEL Parameter?
27. Explain MSGLEVEL(0,1), MSGLEVEL(0,2), MSGLEVEL(1,1),
MSGLEVEL(1,2), MSGLEVEL(2,1),MSGLEVEL(2,2).
28. What is COND Parameter?
29. What is meant by Return code?
30. RC=0, RC=8 , RC>8 , RC=3000 explain it
31. What is the range of the RC (0-4095)
32. Explain TIME Parameter

33. How do terminate a job? (3 methods COND, // , TIME)
34. Explain RESTART Parameter
35. Explain TYPERUN Parameter
36. What is HOLD and SCAN ?
37. Explain ADDRSPC Parameter
38. What is REAL and VIRT? (Default is VIRT)
39. Explain REGION Parameter
40. Explain NOTIFY Parameter
41. List all JOB Parameters.
42. What is EXEC Statement? How many EXEC statement allowed in a JCL?
43. What is PGM, PROC, PARM, COND and TIME Parameters?
44. Explain ONLY / EVEN in COND Parameter.
45. What is the difference between JOB COND and EXEC COND parameters?
46. What us PARM Parameter? Can u explain it with a COBOL Program?
47. What is DD Stands for?
48. Explain the DD statement rules
49. What is the difference between DD Statement and PARM statement (3 points)
50. What is the difference between DD * , DD Data and DUMMY statement.

MVS QUESTIONS

2009-08-21T20:27:00.000-07:00

MVS QUESTIONS

1. What is Mainframe ?
2. What is System SW and Application SW?
3. Clasify IBM’s Operating Systems
4. What is Virtual Machine?
5. What are the classification of MVS
6. What is MVS/ESA ?
7. What are the specialities of MVS/370 System?
8. What are the 3 type of Memory available?
9. What are the two type of Secondary Storage device?
10. What is Channel?
11. What are main characteristics of mainframe computers?
12. What is Virtual Storage?
13. What is Multiprogramming?
14. What is Spooling?
15. What is Batch Processing?
16. What is Time Sharing?
17. What is Logical Transfer and Physical Transfer of data?
18. What is Direct and Indirect method of data transfer?
19. What is Paging System?
20. What is Swapping System?
21. What is Fore-ground processing and Back-ground processing?
22. What is meant Volume?
23. What is meant by Unit?
24. What is meant by Disk?
25. What is meant by Tracks?
26. What is meant by Cylinder?
27. What is meant by DASD?
28. What is DATASET?
29. What is Label? What are the 2 types of labels?
30. What is DASD Lable and what are the 2 types of DASD Lable.
31. What is Tape Label?
32. What is Volume Label?
33. What is File Label?

34. What is meant by VTOC and DSCB?
35. What is CATALOG?
36. What are the 2 types of CATALOGS?
37. What is Master Catalog?
38. What is User Catalog?
39. Are 2 Master Catalogs available in one system?
40. What is OS Catalog?
41. What is VSAM Catalog?
42. What is ICF?
43. What is VDDS / SDDS?
44. What is SYSADM?
45. what are the DATA SET Organisation types available?
46. What is Non-VSAM?
47. What is VSAM ?
48. What is PS,IS,DA and PDS?
49. What are types dataset available in VSAM?
50. What is EDS,KSDS,RRDS and LDS?
51. What is AMS (Access Method Service)? Explain its 3 steps.

J

vsam interview questions

2009-08-21T20:23:00.000-07:00

State whether the following statement is true or false? SHAREOPTS is a parameter in the DEFINE and specifies how an object can be shared among users.
	Choice 1	True
	Choice 2	False

2	How are different versions of GDG named ?
	Choice 1	base-file-name.GnnnnnV00
	Choice 2	GnnnnnV00.ase-file-name
	Choice 3	base-file-name(nnn)
	Choice 4	None of the options listed for this question

3	During processing of a VSAM file, some system error occurs and it is subsequently unusable. What do you do?
	Choice 1	Run VERIFY
	Choice 2	Restart
	Choice 3	Run REPAIR
	Choice 4	None of the options listed for this question

4	Choose the correct one.
	Choice 1	Record in a KSDS file cant be deleted.
	Choice 2	Record in a ESDS file can’t be deleted.
	Choice 3	Record in a ESDS file can’t be rewritten.
	Choice 4	None of the other options listed for this question.

5	Recordsize (80,100) denotes
	Choice 1	Record of Fixed Record length
	Choice 2	Record Variable Record length
	Choice 3	Depends on the type of VSAM dataset viz. KSDS, RRDS, ESDS.
	Choice 4	None of the other options listed for this question.

6	State whether the following statement is TRUE or FALSE VSAM datasets can be stored on TAPE devices.
	Choice 1	True
	Choice 2	False

7	VSAM file-status 23 is
	Choice 1	Duplicate record condition
	Choice 2	End of file condition reached
	Choice 3	Record Not found condition
	Choice 4	Out of Space condition reached

8	How does the current generation be referred ?
	Choice 1	Filename(1)
	Choice 2	Filename(-)
	Choice 3	Filename(0)
	Choice 4	None of the options listed for this question

9	How do you load a VSAM data set with records ?
	Choice 1	Using the REUSE command.
	Choice 2	Using the LOAD command.
	Choice 3	Using the REPRO command.
	Choice 4	None of the options listed for this question

10	Identify the point that is NOT true w.r.t. CI and CA splits in a VSAM file?
	Choice 1	A Control Interval (CI) split occurs if there is insufficient free space available in the CI for a new record (or to extend an existing record). A Control Area (CA) split occurs if there are no free CI's within a CA.
	Choice 2	When a CI split occurs,one of the free CI's within the same CA will be used.
	Choice 3	When a CA split occurs,the new CA is allocated at the end of the existing allocated space, otherwise secondary allocation takes place and the split CA is placed in the secondary extent.
	Choice 4	None of the above

11	Identify the point that is NOT true w.r.t. FileMaxx VSAM Transparency Facility (VTF)
	Choice 1	Most reads and updates are performed randomly (as is typically the case in e-commerce and online transaction processing systems).
	Choice 2	Batch programs that must read entire VSAM files sequentially are already, or can easily become, insensitive to the order in which records are returned.
	Choice 3	Each VSAM file may consist of many different kinds (or types) of records, each having a different record length. However, all records of the same type have the same, or nearly the same, length.
	Choice 4	None of the above

12	The following point(s) is/are true w.r.t. Record Level Sharing(RLS) in VSAM
	Choice 1	RLS addresses physical data integrity issues, such as read consistency, record locking and system logging. But it does not address logical issues, such as enforcement and protection of "business" or "integrity" rules.
	Choice 2	Under RLS, VSAM retains most of its functional limitations. VSAM does not support multiple-field composite keys, multiple-valued keys, NULL-suppressed keys, and/or non-unique alternate indexes with unlimited occurrences of the same key value. Each VSAM index remains confined to a single base cluster, and cannot extend across cluster boundaries.
	Choice 3	Under RLS, VSAM retains an underlying architecture that is not appropriate for relational/SQL processing. Although third party products allow SQL queries of VSAM files, VSAM itself is not well suited to such queries.
	Choice 4	All the above

13	The following procedure can be used for renaming a VSAM file in z/OS
	Choice 1	RENAME - SYSED.MYNAME.DATA.CLUSTER - NEWNAME(SYSED.YOURNAME.DATA) - CATALOG(CATALOG.zOS.MASTER)
	Choice 2	ALTER - SYSED.MYNAME.DATA.CLUSTER - NEWNAME(SYSED.YOURNAME.DATA) -
	Choice 3	ALTER - SYSED.MYNAME.DATA.CLUSTER - NEWNAME(SYSED.YOURNAME.DATA) - CATALOG(CATALOG.zOS.MASTER)
	Choice 4	ALTER - SYSED.MYNAME.DATA.CLUSTER - NEWNAME(YOURNAME) - CATALOG(CATALOG.zOS.MASTER)

14	The command that is used to keep the HURBA in sync between the catalog entry for the VSAM dataset and the VSAM cluster is:-
	Choice 1	VERIFY
	Choice 2	CHECK DATA
	Choice 3	Done automatically by the system
	Choice 4	None of the other options listed for this question.

15	In which of the following scenarios "result-level" locking can be applied?
	Choice 1	A bank typically does not accept transactions that withdraw money from non-existent accounts.
	Choice 2	A vendor typically does not honor orders placed by fictitious customers for merchandise the vendor does not provide.
	Choice 3	A company may delete a customer only if it has no outstanding unpaid invoices.
	Choice 4	All the above

Noida Bhopal Chennai Bangalore New Delhi Chandigarh Coimbatore Vadodara Mumbai mainframe companies

2009-04-16T10:24:00.000-07:00

All e Technologies
Specialization: Enterprise Business Solution (ERP) Customer Relationship Management
(CRM) Business Intelligence Solutions Internet Business Solution
Website: www.alletec.com
Email: amian@alletec.com
Location: Noida

All India Society For Electronics & Computer Technology (AISECT)
Specialization: IT Education & Training IT Consulting e-governance Hardware Support
& Installation Insurance & Financial Services
Website: www.aisect.org
Email: aisect_bpl@sancharnet.in
Location: Bhopal

Allsec Technologies Ltd
Specialization: Inbound Customer Service Accounting Help Desks Tele Services -
Inbound & Outbound Quality Management & Satisfaction Surveys Tech Support Help
Desks.
Website: www.allsectech.com
Email: svan@allsectech.com
Location: Chennai

ALSTOM Projects India Limited
Specialization: Supervisory Control and Data Acquisition System (SCADA) for Power
and Industrial Processes, Terminal Automation System for Oil / Gas sector, Product
development for Real Time application
Website: www.alstom.com
Email: anil.chaudhry@tde.alstom.com
Location: Noida

Amadeus India Pvt Ltd
Specialization: - IT Consulting & BPO, Process Services, Hardware Support &
Installation, IT Training & Education
Email: rbansal@amadeus.co.in
Location: New Delhi
America Online Member Services India Pvt. Ltd.
Specialization: IT Enabled Services
Website: www.aol.com
Email: ptrsnae@aol.com
Location: Bangalore

American Express (India) Pvt. Ltd.
Specialization: Data Management and Information Analysis & Control
Website: www.americanexpress.com
Email: minnie.m.mehta@aexp.com
Location: New Delhi

American Megatrends (India) Pvt. Ltd.
Specialization: BIOS Customisation Device Driver & Firmware Development Embedded
Solutions Storage Solutions E-Commerce and Web related projects
Website: www.amiindia.co.in
Email: CEO@amiindia.co.in
Location: Chennai

American Software & Global Technology (P) Ltd
Specialization: ASgT serves government agencies and commercial companies of all sizes
in sectors such as: Health Care, Financial Services, Manufacturing, Distribution & Retail,
Utilities and Telecommunications. Also offering BPO services like trascription, Data
entry, Ebooks services and Call center services
Email: mangatrandhir@hotmail.com
Location: Chandigarh

Amoeba Telecom
Specialization: Telecom Billing Retail and Whole Sale Billing Intelligent Routing
Website: www.isoftel.com
Email: siva@isoftel.com
Location:

Amsoft Systems India Inc.
Specialization: Enterprise Solutions Service Provider Solutions Business Network
Solutions
Website: www.amsoftindia.com
Email: raghu.nayyar@amsoft.net
Location: New Delhi

Anjaleem Enterprises Pvt. Ltd.
Specialization: Call Metering Subscriber end Telecom Product Real Time Software
Email: mailbox@anjaleem.com
Location:

Annet Communications Pvt Ltd
Specialization: eBusiness Solutions Multimedia Applications Development Client Server
Application Technology Consulting Wireless Applications
Website: www.annetsite.com
Email: rohanbul@annetsite.com
Location: Mumbai

mainframes companies in Bangalore Gurgaon Mumbai Chennai

2009-04-16T10:22:00.000-07:00

Ajax.com Private Limited
Specialization: - Medical Transcription
Email: mundra@ajaxdotcom.net
Location: Bangalore

Ajuba Solutions (India) Pvt. Ltd.
Specialization: - Healthcare - Collections and Accounts Receivables Management -
Insurance - Call center services - Transaction Processing (Data Entry/ Conversion,
Database Creation, Claim Processing) - Customer Interaction (Telemarketing) - Analytics
(Market Research, Coding) - Call Center Services
Website: www.ajubanet.net
Email: shankar.n@ajubanet.net
Location: Chennai

Akshar Infotech (A Division of NOM Enterprise Pvt Ltd.)
Email: mail@aksharinfo.com
Location: Vadodara

Alcatel Development Centre Chennai (P) Ltd
Specialization: Software Development
Website: www.alcatel.be
Email: kv.lakshminarayanan@adcc.alcatel.be
Location: Chennai

Alcatel India Limited
Specialization: Intelligent Networks Solutions Messaging Systems Networking
Management Systems
Website: www.alcatel.com
Email: Subhash.Bana@alcatel.fr
Location: Gurgaon

Alden Prepress Services Pvt Ltd
Specialization: The initial focus is on developing APPS into a world class production
base for electronic publishing especially scientific and academic books and journals.
Capacities will be continuously enhanced to meet the growing business from US clients,
the logical movements forward will be Editorial base, Typesetting base, Template and
Software Enhancement base, Customer Relationship Management base and possibly
Printing base over a 5-7 year period. Developing and sustaining a quality management
system under ISO 9000 will be crucial ingredient in the corporate growth.
Website: www.alden.co.in
Email: ranjana@alden.co.in

Location: Chennai
Algorithms Software Pvt. Ltd.
Specialization: Software Development & Consultancy
Website: www.algosoftware.com
Email: info@algosoftware.com
Location: Mumbai

Mumbai Ahmedabad Bangalore Gurgaon mainframe company contact details

2009-04-16T10:21:00.000-07:00

Aftek Infosys Ltd
Specialization: Aftek’s core competence lies in the areas of Embedded (real-time
operating systems & kernels, networking & communication protocol stacks), Systems
(graphics engines and networking systems, encryption, compression & search
techniques), Mobile & Wireless (web-enabled, mobile applications, internet protocol
suites, GSM, GPRS &3G) and Web (component-based, 3-tier applications, online
collaborative e-business portals). With core competence in these areas, Aftek is focusing
on three of the most critical components of Enterprise Business Management – processes,
infrastructure and information management.
Website: www.aftek.com
Email: ranjitd@aftek.com
Location: Mumbai

Agarwal Management Consultants Pvt. Ltd.
Website: www.agarwalmanagement.com
Email: alpana@agarwalmanagement.com
Location: Ahmedabad

Agere Systems India Pvt Ltd
Specialization: Telecom Software and Design Research & Development
Website: www.agere.com
Email: ramki@agere.com
Location: Bangalore

Airline Financial Support Services (I) Pvt. Ltd.
Specialization: IT Enabled Services
Website: www.airlinefinancial.com
Email: kmistry@afs-ites.com
Location: Mumbai

Aithent Technologies Pvt Ltd.
Specialization: Services — Outsourcing And Managed Services, Software Development
And Support Services, Re-Engineering And Documentation Services. Products — Fraud
Prevention And Investigation Tool, Regulatory And Compliance Solution, E-Governance
Tools, Knowledge And Project Management System, ERP , Collaborative Tools

Embedded — Hardware Design (PCB, FPGA/CPLD And ASIC), Device Drivers For
Varied OS And Target Platforms, Real Time Software Applications, Systems Integration,
Risk Analysis And Management Of Real Time Systems, Quality Assurance, Testing And
Benchmarking. IT Education —Software Development Life Cycle Management, OOAD
And UML , CMM Testing , Project Management Soft Skills, R & D And Consultancy.
Website: www.aithent.com
Email: sesha@ggn.aithent.com
Location: Gurgaon

Noida Secunderabad Hyderabad Pune Chennai Bangalore mainframes company details

2009-04-16T10:19:00.000-07:00

Adobe Systems India Pvt Ltd
Specialization: Web and Desktop Publishing Software
Website: www.adobeindia.com
Email: ngupta@adobe.com
Location: Noida

ADP India Dealer Services Pvt Ltd
Email: ayush_maheshwari@adp.com
Location: Secunderabad

ADP Wilco (India) Private Limited
Specialization: - Software Development for Wilco Products - Software Development for
Wilco Clients - I.T.Enabled Services - Business Consultancy
Website: www.wilco-int.com
Email: bbalaji@wilco-int.com
Location: Hyderabad

Advent Software Limited
Specialization: - Distributed process integration in B2B systems - Healthcare verticals -
Smartcard technology based turnkey solutions - Payment gateways
Website: www.adventsoftware.net
Email: sanjeev@adventsoftware.net
Location: Pune

AdventNet Development Centre (India ) Pvt Ltd
Specialization: Network Management Solutions for OEM Network Management
Solutions for Enterprises
Website: www.adventnet.com
Email: sunil@adventnet.com
Location: Chennai

Affinity Software
Specialization: Web Technologies: Internet Agents, ASP, JavaScript, VBScript, XML
Application Development and Maintenance Oracle, SQL Server, MySQL JBuilder,
VC++ Domains SCM and ERP
Website: www.affinity-soft.com
Email: affinity-soft@affinity-soft.com
Location: Bangalore

kolkata chennai hyderabad nagpur bangalore mainframes company details

2009-04-16T10:17:00.000-07:00

ACES Infotech Pvt Limited
Specialization: School Computer Education (including Turnkey Projects) Corporate IT
Training Software Development - IT Courseware Planning & Development Hardware
Service / Maintenance & Sales
Website: www.acesinfotech.com
Email: aces@cal.vsnl.net.in
Location: Kolkata

Acsys Software (India) Pvt Ltd
Specialization: Mutual Fund Unit Registry, Shareholder Record Keeping and Transaction
Processing Software for the Global Fund Industry. Mutual Fund Distributor’s Software
package for the front office activities and back office commission computing/reconciling
activities. Portfolio Management, Insurance and Pension Funds Management Software
packages. IT enabled Transaction Processing BPO activities for the Global Financial
Industry.
Website: www.acsysindia.com
Email: rvetrivel@acsysindia.com
Location: Chennai

Acumen Software Technologies Ltd
Specialization: - Web based sales and distribution software platform - Integration with
ERPs like SAP, BaaN, Oracle etc.
Website: www.acumensoftware.net
Email: info@acumensoftwarelimited.com
Location: Hyderabad

ADCC Research & Computing Centre Ltd
Specialization: Geographical Information System (GIS) based applications Integrated
GIS,GPS,GSM,VHF Tracking solutions Multi tier Business applications including CTI
and Mobile applications E-Commerce solutions (B2B, B2C,G2C)
Website: www.adccindia.com
Location: Nagpur

Aditi Technologies Pvt Ltd
Specialization: - Custom application development - Software Testing Services -
Outsourced Product Development for software companies - Software Integration Services
Website: www.aditi.com
Email: ravi@aditi.com
Location: Bangalore

mainframes companies in chennai pune mumbai bangalore

2009-04-16T10:16:00.000-07:00

Accel Software and Technologies Limited
Specialization: Accel STL is a group company of Accel, which is one of India’s fastest
growing Infotech groups with a turnover of US $ 50 million. Accel STL offers end-toend
solutions for various software applications, VLSI & Embedded Systems using cutting
edge technologies.
Website: www.accelstl.com
Email: badri@accel-india.com
Location: Chennai

AccelTree Software Pvt Ltd
Specialization: Outsourced software development services, Packaged Software Products,
Development tools, Product integration
Website: www.acceltree.com
Email: sunil.kumar@acceltree.com
Location: Pune

Accenture Services Pvt. Ltd.
Specialization: Project deliver, Custom application development, Application
management & conversion, Creation of client-specific facilities, Consulting , outsourcing
Website: www.accenture.com
Email: sandeep.sekhar@accenture.com
Location: Mumbai

ACCPAC India Private Limited
Specialization: - Enterprise Resource Planning, Small, Medium & Large Corporates -
eCRM
Website: www.accpac.com
Email: siv.m@accpacindia.com
Location: Bangalore

Ace Software Exports Ltd
Specialization: AM/FM CAD Conversion & GIS Solutions. Creation of Electronic
Database & eBook. Internet Solutions, Client / Server Solutions on Microsoft® Platform.
Web Development and Web Promotions.
Website: www.acesoftex.com
Location: Rajkot

Aces Global Systems Pvt. Ltd
Specialization: Offshore development, Staff Augmentation, Project Consulting, Systems
Integration
Website: www.acesintl.com
Email: salil@acesintl.com
Location: Mumbai

mainframes companies in mumbai bangalore newdelhi

2009-04-16T10:14:00.000-07:00

24/7 Customer.com

Specialization: BPO services, Voice Based Phone Support (Inbound & Outbound),

Telemarketing/Telesales (Inbound & Outbound), Email Based Support, Live Chat

Website: www.247customer.com

Email: nags@247customer.com

Location: Bangalore

3D PLM Software Solutions Ltd.

Specialization: Software Development, PLM/CAD/CAM, Customization Services

Website: www.3dplmsoftware.com

Email: manup@geometricsoftware.com

Location: Mumbai

A G Technologies Pvt Ltd

Specialization: SAP Implementation and Post Implementation Services Client / Server

and Internet Application, Development Multimedia Solutions

Website: www.ag-technologies.com

Email: anish.goenka@ag-technologies.com

Location: Mumbai

Aalayance Ecom Services Pvt Ltd

Specialization: EAI Business Integration Business Process Modelling ERP CRM

PKI/Security Wireless Portal Solutions eLearning Directory Services

Website: www.aalayance.com

Email: msuresh@aalayance.com

Location: Bangalore

ABM Knowledgeware Ltd

Specialization: Software & Services Group Apex Administrative & Policy making

Offices of State Government Treasury Operations Municipal Corporation (Utilities,

Consumer Services, Accounts, Revenue) Revenue Administration up-to Village level in

District Banks Financial Institutions System Integration Group Banks Corporate Defence

Education & Research Government Hospitals Small & Medium Enterprises

Website: www.abmindia.com

Email: prane@abmindia.com

Location: Mumbai

ABO Software Private Limited

Website: www.abosoftware.com

Email: ajayksanghi@abosoftware.com

Location: New Delhi

mainframe cobol programes for reversing the test and display,testing multiple conditions

2008-12-26T03:21:00.000-08:00

Reversing the test and display.

004100 DISPLAY-THE-WORDS.

004200

004300 DISPLAY "The words sorted in ASCII order are:".

004400 IF WORD-1 <>

004500 DISPLAY WORD-1

004600 DISPLAY WORD-2.

004700 IF WORD-1 NOT <>

004800 DISPLAY WORD-2

004900 DISPLAY WORD-1.

You should also try a version of wrdsrt01.cbl that tests incorrectly in DISPLAY-THE-WORDS, This version tests for LESS THAN and GREATER THAN. Try coding this one as badsrt.cbl and satisfy yourself that the results are identical unless you enter the exact string for WORD-1 and WORD-2, such as ABC and ABC. Note that the test fails to display anything for this condition.

An incorrect version of the test.

004100 DISPLAY-THE-WORDS.

004200

004300 DISPLAY "The words sorted in ASCII order are:".

004400 IF WORD-1 <>

004500 DISPLAY WORD-1

004600 DISPLAY WORD-2.

004700 IF WORD-1 > WORD-2

004800 DISPLAY WORD-2

004900 DISPLAY WORD-1.

The indentation chosen for the IF is completely arbitrary. As long as the IF starts in and stays within Area B, the arrangement is up to you. Listing 4.8 and Listing 4.9 are equally valid, but in Listing 4.9 it is difficult to tell what is going on, and Listing 4.8 looks a bit sloppy.

DO/DON'T:
DO indent IF conditions carefully. An IF controls all statements up to the period at the end of the sentence.

DON'T use sloppy indenting on an IF. Correct indentation gives a good visual clue of which parts of the program are controlled by the IF.

Sloppy indenting of an IF.

004100 DISPLAY-THE-WORDS.

004200

004300 DISPLAY "The words sorted in ASCII order are:".

004400 IF WORD-1 <>

004500 DISPLAY WORD-1

004600 DISPLAY WORD-2.

004700 IF WORD-1 NOT <>

004800 DISPLAY WORD-2

004900 DISPLAY WORD-1.

Failing to indent an IF.

004100 DISPLAY-THE-WORDS.

004200

004300 DISPLAY "The words sorted in ASCII order are:".

004400 IF WORD-1 <>

004500 DISPLAY WORD-1

004600 DISPLAY WORD-2.

004700 IF WORD-1 NOT <>

004800 DISPLAY WORD-2

004900 DISPLAY WORD-1.

Testing Multiple Conditions

An IF test also can be used to test more than one condition. Conditions can be combined by using AND, OR, or combinations of both. Listing 4.10 is a short menu program. A menu program is designed to display a series of options on the screen and let the user pick one option to execute. In this menu program, the user has a choice of displaying one of three possible messages.

Combining tests using OR.

000100 IDENTIFICATION DIVISION.

000200 PROGRAM-ID. MENU01.

000300*------------------------------------------------

000400* THIS PROGRAM DISPLAYS A THREE CHOICE MENU OF

000500* MESSAGES THAT CAN BE DISPLAYED.

000600* THE USER ENTERS THE CHOICE, 1, 2 OR 3, AND

000700* THE APPROPRIATE MESSAGE IS DISPLAYED.

000800* AN ERROR MESSAGE IS DISPLAYED IF AN INVALID

000900* CHOICE IS MADE.

001000*------------------------------------------------

001100 ENVIRONMENT DIVISION.

001200 DATA DIVISION.

001300 WORKING-STORAGE SECTION.

001400

001500 01 MENU-PICK PIC 9.

001600

001700 PROCEDURE DIVISION.

001800 PROGRAM-BEGIN.

001900

002000 PERFORM GET-THE-MENU-PICK.

002100

002200 PERFORM DO-THE-MENU-PICK.

002300

002400 PROGRAM-DONE.

002500 STOP RUN.

002600

002700* LEVEL 2 ROUTINES

002800 GET-THE-MENU-PICK.

002900

003000 PERFORM DISPLAY-THE-MENU.

003100 PERFORM GET-THE-PICK.

003200

003300 DO-THE-MENU-PICK.

003400 IF MENU-PICK <>

003500 MENU-PICK > 3

003600 DISPLAY "Invalid selection".

003700

003800 IF MENU-PICK = 1

003900 DISPLAY "One for the money.".

004000

004100 IF MENU-PICK = 2

004200 DISPLAY "Two for the show.".

004300

004400 IF MENU-PICK = 3

004500 DISPLAY "Three to get ready.".

004600

004700* LEVEL 3 ROUTINES

004800 DISPLAY-THE-MENU.

004900 DISPLAY "Please enter the number of the message".

005000 DISPLAY "that you wish to display.".

005100* Display a blank line

005200 DISPLAY " ".

005300 DISPLAY "1. First Message".

005400 DISPLAY "2. Second Message".

005500 DISPLAY "3. Third Message".

005600* Display a blank line

005700 DISPLAY " ".

005800 DISPLAY "Your selection (1-3)?".

005900

006000 GET-THE-PICK.

006100 ACCEPT MENU-PICK.

006200

Here are sample output results from menu01.cbl for a valid and an invalid response:

OUTPUT:

Please enter the number of the message

that you wish to display.

1. First Message

2. Second Message

3. Third Message

Your selection (1-3)?

Two for the show.

Please enter the number of the message

that you wish to display.

1. First Message

2. Second Message

3. Third Message

Your selection (1-3)?

Invalid selection

ANALYSIS: The valid menu selections are 1, 2, and 3. The test that the value entered is in a range at lines 003400 through 003500, ending with a display of an invalid entry message at line 003600. If the entered MENU-PICK is less than 1 or greater than 3, it is invalid. Note that the OR on line 003400 combines the two tests within one IF. An OR test is true if either of the tests is true.

Read the comments in the program, because they explain some of the options used to improve the look of the displayed menu. The levels in the comments relate to the level of PERFORM. Routines in level 2 are being performed from the top level of the program, PROGRAM-BEGIN. Routines in level 3 are performed from within routines at level 2.

An AND test is true only if both conditions being tested are true. Listing 4.11 asks the user to enter a number between 10 and 100, excluding 10 and 100. Therefore, the valid range of entries for this program is 011 through 099. Remember that ACUCOBOL will require that you enter the leading zero.

cobol program to diplay two words in ascii order and analysing that

2008-12-26T02:52:00.000-08:00

Displaying two words in ASCII order.

000100 IDENTIFICATION DIVISION.

000200 PROGRAM-ID. WRDSRT01.

000300*----------------------------------------------

000400* Accepts 2 words from the user and then displays

000500* them in ASCII order.

000600*----------------------------------------------

000700 ENVIRONMENT DIVISION.

000800 DATA DIVISION.

000900 WORKING-STORAGE SECTION.

001000

001100 01 WORD-1 PIC X(50).

001200 01 WORD-2 PIC X(50).

001300

001400 PROCEDURE DIVISION.

001500 PROGRAM-BEGIN.

001600

001700 PERFORM INITIALIZE-PROGRAM.

001800 PERFORM ENTER-THE-WORDS.

001900 PERFORM DISPLAY-THE-WORDS.

002000

002100 PROGRAM-DONE.

002200 STOP RUN.

002300

002400* Level 2 Routines

002500

002600 INITIALIZE-PROGRAM.

002700 MOVE " " TO WORD-1.

002800 MOVE " " TO WORD-2.

002900

003000 ENTER-THE-WORDS.

003100 DISPLAY "This program will accept 2 words,".

003200 DISPLAY "and then display them".

003300 DISPLAY "in ASCII order.".

003400

003500 DISPLAY "Please enter the first word.".

003600 ACCEPT WORD-1.

003700

003800 DISPLAY "Please enter the second word.".

003900 ACCEPT WORD-2.

004000

004100 DISPLAY-THE-WORDS.

004200

004300 DISPLAY "The words in ASCII order are:".

004400

004500 IF WORD-1 > WORD-2

004600 DISPLAY WORD-2

004700 DISPLAY WORD-1.

004800

004900 IF WORD-1 NOT > WORD-2

005000 DISPLAY WORD-1

005100 DISPLAY WORD-2.

005200

Here is the sample output of wrdsrt01.cbl when the words entered are beta and alpha:

OUTPUT:

This program will accept 2 words,

and then display them

in ASCII order.

Please enter the first word.

beta

Please enter the second word.

alpha

The words in ASCII order are:

alpha

beta

ANALYSIS: Multiple statements are executed within the IF tests at lines 004500 and 004900. There are two DISPLAY statements under each of the IF tests. If WORD-1 is greater than WORD-2, or if WORD-1 occurs after WORD-2 in the ASCII sorting sequence, WORD-2 is displayed first.

You should edit, compile, and run wrdsrt01.cbl; then try it with various pairs of "words," such as ABC and abc, (space)ABC and ABC, or ABCD and ABC, to see how these are arranged in ASCII order.

Please note that many people, including experienced programmers, assume that the opposite of GREATER THAN is LESS THAN. However, testing for only these two conditions misses the case where the two entered words are identical. The complement of GREATER THAN is LESS THAN OR EQUAL which is correctly stated as NOT GREATER THAN.

You also can try a version of wrdsrt01.cbl that reverses the test in DISPLAY-THE-WORDS, as in Listing 4.6, which is just a listing of the DISPLAY-THE-WORDS paragraph. Try coding this one as wrdsrt02.cbl and satisfy yourself that the results are identical. Note that the test and display order are reversed.

testing an if statement in cobol,writing the rest of the if,COBOL comparison operators.

2008-12-26T02:45:00.000-08:00

What Can You Test with IF

The condition in an IF verb is a test of one value against another for equality or inequality.

New Term: The symbols used to compare two values are called comparison operators. The short and long versions of these comparisons are all comparison operators. IS NOT EQUAL, NOT =, =, IS EQUAL, NOT <, >, GREATER THAN, and NOT GREATER THAN are all examples of comparison operators. Tables 4.1 and 4.2 list all of the comparison operators.

Table 4.1 lists the comparisons that can be made and describes their effects.

COBOL comparison operators.

Comparison Operator	Description
IF x IS EQUAL y	True if x equals y
IF x IS LESS THAN y	True if x is less than y
IF x IS GREATER THAN y	True if x is greater than y
IF x IS NOT EQUAL y	True if x does not equal y
IF x IS NOT LESS THAN y	True if x is not less than y (or is equal to or greater than y)
IF x IS NOT GREATER THAN y	True if x is not greater than y (or is equal to or less than y)

The word IS in a comparison is optional, and EQUAL, GREATER THAN, and LESS THAN can be shortened to =, >, and <, respectively. Table 4.2 compares the possible versions of comparisons.

More COBOL comparison operators.

Optional Operator	Shortest Version
IF x EQUAL y	IF x = y
IF x LESS THAN y	IF x <>
IF x GREATER THAN y	IF x > y
IF x NOT EQUAL y	IF x NOT = y
IF x NOT LESS THAN y	IF x NOT <>
IF x NOT GREATER THAN y	IF x NOT > y

Listing 4.4 repeats yesno03.cbl, using the shortened comparisons.

yesno03.cbl with shorter comparisons.

000100 IDENTIFICATION DIVISION.

000200 PROGRAM-ID. YESNO04.

000300*--------------------------------------------------

000400* This program asks for a Y or N answer, and then

000500* displays whether the user chose yes or no.

000600* The edit logic allows for entry of Y, y, N, or n.

000700*--------------------------------------------------

000800 ENVIRONMENT DIVISION.

000900 DATA DIVISION.

001000 WORKING-STORAGE SECTION.

001100

001200 01 YES-OR-NO PIC X.

001300

001400 PROCEDURE DIVISION.

001500 PROGRAM-BEGIN.

001600

001700 PERFORM GET-THE-ANSWER.

001800

001900 PERFORM EDIT-THE-ANSWER.

002000

002100 PERFORM DISPLAY-THE-ANSWER.

002200

002300 PROGRAM-DONE.

002400 STOP RUN.

002500

002600 GET-THE-ANSWER.

002700

002800 DISPLAY "Is the answer Yes or No? (Y/N)".

002900 ACCEPT YES-OR-NO.

003000

003100 EDIT-THE-ANSWER.

003200

003300 IF YES-OR-NO = "y"

003400 MOVE "Y" TO YES-OR-NO.

003500

003600 IF YES-OR-NO = "n"

003700 MOVE "N" TO YES-OR-NO.

003800

003900 DISPLAY-THE-ANSWER.

004000 IF YES-OR-NO = "Y"

004100 PERFORM IT-IS-VALID

004200 DISPLAY "You answered Yes.".

004300

004400 IF YES-OR-NO = "N"

004500 PERFORM IT-IS-VALID

004600 DISPLAY "You answered No.".

004700

004800 IT-IS-VALID.

004900 DISPLAY "Your answer is valid and".

005000

For numeric values, all these tests make sense. Less than and greater than are both conditions that easily can be established when you are testing two numbers. But what are you testing when you compare two alphanumeric variables?

When a condition test is performed on alphanumeric variables, the tests usually compare the characters in the two alphanumeric values on the left and right sides of the comparison operator, in ASCII order. (See Appendix B, "ASCII.")

New Term: The sequence in which the characters appear in the ASCII chart is known as the ASCII collating sequence. Collate means to assemble in some sort of order--in this case, ASCII order.

ASCII is not the only collating sequence. IBM mainframes use a collating sequence called EBCDIC. In the ASCII collating sequence, numbers appear before uppercase letters, and uppercase letters appear before lowercase letters. In the EBCDIC collating sequence, lowercase letters appear before uppercase letters and numbers appear last. Punctuation characters vary quite a bit in the EBCDIC and ASCII collating sequences. Collating sequences also vary for different spoken languages. Castillian Spanish treats the letter combinations ch and ll as single letters so that llanero sorts after luna and chico sorts after corazon. The examples in this book are based on the English ASCII collating sequence.

In ASCII order, A is less than B, AB is less than ABC, and the uppercase letters are less than the lowercase letters; so, ABC is less than abc. When an alphanumeric variable contains the digits 0 through 9, the digits are less than the characters, so 1BC is less than ABC. Spaces are the lowest of all, so three spaces are less than 00A. Refer to Appendix B for the complete set and sequence of ASCII characters.

Listing 4.5 will accept two words from a user and then display them in ASCII order. You can use this program any time you want to find out the actual ASCII order for two values. The testing is done in the paragraph DISPLAY-THE-WORDS, which starts at line 004100. The actual tests, at lines 004500 and 004900, use a greater than (>) and a not greater than (NOT >) comparison to decide which word to display first.