Mainframe230

IMS DB/DC Return Codes

noreply@blogger.com (M siva raman) — Fri, 08 Apr 2011 17:12:00 +0000

The IMS return codes are listed here alphabetically, you may browse through them or you may enter the code you are looking for and press the enter key to go directly to the error message.

Explanation: IMS ignored a CHNG or ISRT call because the response alternate PCB referenced in the call specified a transaction code as a destination. A response alternate PCB must have a logical terminal specified as its destination.

Programmer Response: Correct the CHNG or ISRT call.

Explanation: An I/O area is required as one of the parameters on this call and the call did not specify one. After this status code is returned, your position in the database is unchanged.

Programmer Response: Correct the call by including the address of an I/O area as one of the call parameters.

Explanation: For call-level programs: There is an error in an SSA for a DLET, a get, an ISRT, or a REPL call for one of these reasons:

· DL/I could not find a segment in the DB PCB specified in the call that has the segment name given in the SSA.

· The segment name is in the DB PCB, but the SSA specifying that segment name is not in its correct hierarchic sequence.

· The call specifies two SSAs for the same hierarchic level.

IMS also returns this status code when a STAT call has an invalid statistics function. After this status code is returned, your position in the database is unchanged.

For command-level programs: There is an error in one of WHERE or SEGMENT options on a get or ISRT command for one of these reasons:

· DL/I could not find a segment in the DB PCB specified in the segment name given in the SEGMENT option.

· The segment name is in the DB PCB, but the qualification for the command does not specify it in its correct hierarchic sequence.

· The command specifies two SEGMENT options for the same hierarchic level.

Programmer Response: Correct the segment name in the SSA or SEGMENT option or the statistics function in the STAT call.

Explanation: For call-level programs: Either the function parameter on the call is invalid or the function is not supported for the type of PCB specified in the call. Some possible reasons are:

· The function parameter is invalid.

· A system service call used a PCB that is not the I/O PCB.

· A message GU or GN call used an alternate PCB instead of the I/O PCB.

· A database call used a PCB that is not a DB PCB.

· A message GU used the I/O PCB without specifying IN=trancode in the BMP JCL.

· A SETS or ROLS call included the I/O area but omitted the token.

For command-level programs: A command was issued that is not supported in the environment; for example, a system service command in an online program. If the command is correct, some other possible causes are:

· Referencing a DB PCB on a system service command. System service commands must reference the I/O PCB.

· Referencing an I/O PCB for a database command, or not defining an I/O PCB before issuing system service commands.

Programmer Response: Be sure that the function specified is valid for the PCB specified by the request.

Explanation: GSAM detected a variable-length record whose length is invalid on a GU, GHU, GN, or GHN.

Programmer Response: Correct the program.

Explanation: The program issued an ISRT call (load or add) that did not include any SSAs. ISRT calls require SSAs. If the program was issuing a GU call to a GSAM database, the GU did not specify an RSA. RSAs are required on GU calls to GSAM databases. After this status code is returned, your position in the database is unchanged.

Programmer Response: Correct the ISRT call by including a qualification, or correct the GU call by adding an RSA to the call.

Explanation: A data management open error occurred. Some possible reasons are:

· There is an error in the DD statements.

· Neither DD statements nor DFSMDA dynamic allocation members were provided for this database.

· The data set OPEN request did not specify load mode, but the data set was empty. An empty data set requires the load option in the PCB.

· The buffer is too small to hold a record that was read at open time. See the storage estimates in IMS/ESA System Administration Guide for specification of the minimum buffer pool size.

· There were no DD statements or DFSMDA members supplied for logically-related databases.

· For an OSAM data set, the DSORG field of the OSAM DCB, DSCB, or JFCB does not specify PS or DA.

· For an old OSAM data set, the BUFL or BLKSIZE field in the DSCB is zero.

· The data set is being opened for load, and the processing option for one or more segments is other than L or LS.

· The allocation of the OSAM data set is invalid. The allocation is probably (1,,1) rather than (1,1) and this causes the DSORG to be P0.

· The processing option is L, the OSAM data set is old, and the DSCB LRECL and/or BLKSIZE does not match the DBD LRECL and/or BLKSIZE.

· Incorrect or missing information prevented IMS from determining the block size or the logical record length.

· A catalog was not available for accessing a VSAM database that was requested.

· OS could not perform an OPEN, but the I/O request is valid. Either the data definition information is incorrect, or information is missing.

· RACF was used to protect the OSAM data set and the control region has no update authorization.

If IMS returns message DFS0730I, you can determine the cause of the OPEN failure from this message in the job log. For more information, see the description of this message in IMS/ESA Messages and Codes.

Programmer Response: These kinds of problems often require the help of a system programmer or system administrator. But before you go to one of these specialists, there are some things you can do:

· Check the DD statements. Make sure that the ddname is the same as the name specified on the DATASET statement of the DBD. The segment name area in the DB PCB (call level), or in the DIB (command level) has the ddname of the data set that couldn't be opened.

· Check the PSB and make sure that the appropriate processing options have been specified for each of the DB PCBs that your program uses.

Explanation: For call-level programs: For calls such as SETS, ROLS, and INIT that provide parameters in the I/O area, the format of the parameters in the I/O area is invalid.

For database calls such as get, DLET, REPL, and ISRT that include SSAs, the format of one of the SSAs is invalid. The number in the segment level number field of the DB PCB is the level number of the SSA that is invalid. Some possible reasons for the invalid SSA format are:

· The SSA contains a command code that is invalid for that call.

· The relational operator in the qualification statement is invalid.

· A qualification statement is missing a right parenthesis or a Boolean connector.

· A DLET call has multiple or qualified SSAs.

· A REPL call has qualified SSAs.

· An ISRT call has the last SSA qualified.

· An ISRT call that inserts a logical child segment into an existing database includes the D command code. ISRT calls for logical child segments cannot be path calls.

· The RSA parameter on a GSAM call is invalid.

· The SSA used an R, S, Z, W, or M command code for a segment for which there are no subset pointers defined in the DBD.

· The subset command codes included in the SSA are in conflict; for example, if one SSA contained an S status code and a Z status code, Fast Path would return an AJ status code. S means to set the pointer to current position; Z means to set the pointer to zero. You could not use these status codes in one SSA.

· The pointer number following a subset pointer command code is invalid. Either you didn't include a number, or you included an invalid character. The number following the command code must be between 1 and 8, inclusive.

· The SSA included more than one R command code. An SSA may include only one R command code.

· The size specified for the SSA is too small. After this status code is returned, your position in the database is unchanged.

· In response to a SETS or ROLS call, the length of the I/O area is zero, the LL field is less than 4, or the ZZ field is not zero.

· In response to an INIT call, the format of the I/O area is incorrect.

For command-level programs: An ISRT command attempted to insert a logical child segment using a path command. ISRT commands for logical child segments cannot be path commands.

Programmer Response: If you receive this status code on a SETS, ROLS, or INIT request, correct the parameters provided in the I/O area.

If you receive this status code on a get, DLET, REPL, or ISRT request, correct the invalid portion of the SSA. If you receive this status code on a GSAM call, correct the RSA.

Explanation: For call-level programs: An SSA contains an invalid field name: the field name isn't defined in the DBD. The number in the segment level number field of the DB PCB is the level number of the SSA that contains the invalid name.

You can also receive this status code if the program is accessing a logical child through the logical parent. DL/I returns AK if the field specified in the qualification has been defined for the logical child segment, and it includes (at least partially) the portion of the logical child that contains the concatenated key of the logical parent.

When you are using field level sensitivity, a field you specified in the SSA has not been defined in the PSB. After this status code is returned, your position in the database is unchanged.

For command-level programs: A WHERE option contains an invalid field name. (The field name isn't defined in the DBD.) The number in the DIBSEGLV field of the DIB is the level number of the WHERE option that contains the invalid name.

Programmer Response: Correct the SSA or WHERE option.

Explanation: You get this status code if you:

1. Issue a message call in a batch program

2. Issue a ROLB, ROLS, or SETS request from a batch program under one of the following conditions:

o The system log is not on direct access storage.

o The system log is on direct access storage, but dynamic backout has not been specified using the BKO execution parameter.

Programmer Response: For cause 1, correct the program to not issue message calls in a batch program. For cause 2, either change the program or put the log on direct access storage with BKO specified on the execution parameter.

Explanation: The INQY call specifies an invalid function.

Programmer Response: Specify a valid subfunction. Valid INQY call subfunctions are DBQUERY, ENVIRON, or null (8 blanks).

Explanation: For call-level programs: The call function is not compatible with the processing option in the PCB, the segment sensitivity, the transaction-code definition, or the program type. The level number in the PCB is the level number of the SSA that is invalid. Some of the reasons you might get this status code are:

· If you issue a retrieval call with the D command code in a program that doesn't have the P processing option specified in the DB PCB that was used for the call.

· If you issue a DLET or ISRT call to a terminal-related dynamic MSDB from a program with no input LTERM present; for example, a batch-oriented BMP.

· If the subset pointer referenced in the SSA was not defined in the program's PSB. For example, if your program's PSB specifies that your program can use subset pointers 1 and 4, and your SSA referenced subset pointer 5, Fast Path would return an AM status code to your program.

· If your program tried to use an S, Z, W, or M command code for a subset pointer to which it was not pointer update sensitive, as defined in the program's PSB.

· If a BMP, a CICS online program, a CICS shared database program, or an MPP issues an ISRT call with the D command code when the program doesn't have the P processing option specified in the DB PCB that was referenced in the call. Batch programs do not need the P processing option to issue an ISRT call with the D command code--unless the program uses field level sensitivity.

· If the processing option is L and the program issued a call other than an ISRT call. Load programs can issue only ISRT calls.

· If a DLET, REPL, or ISRT call that references a DB PCB doesn't have the necessary processing option for that call. The minimum processing options for these calls are D for DLET; R for REPL; and I for ISRT.

· If you issue a DLET, REPL, or ISRT call for a segment to which the program isn't sensitive.

· If you issue a CHKP call on a GSAM/VSAM data set opened for output.

· If you issue a GSAM call with an invalid call function code.

· If you issue an ISRT or DLET call for the index target segment or a segment on which the index target is dependent in the physical database while using an alternate processing sequence.

· If you issue a path replace where the program does not have replace sensitivity, command code N is not specified, and the data for the segment is changed in the I/O area.

· If you issue a call to a GSAM dummy data set. Any call to a GSAM dummy data set is invalid.

· If GSAM could not obtain buffer space because the region size is too small. This is shown by the value X'1C' in the field GBCRTNCD.

· If you issue a DLET, ISRT, or REPL call from a program where the TRANSACT macro used at IMS system definition specified INQUIRY=YES for the input message.

After this status code is returned, your position in the database is unchanged.

For command-level programs: The command is not compatible with the processing option in the PCB or segment sensitivity. The level number in the DIB is the level number of the qualification that is invalid. Some of the reasons you might get this status code are:

· If you issue a path retrieval command in a program that doesn't have the P processing option specified in the DB PCB that was used for the call.

· If the processing option is L and the program issued a command other than a LOAD command. Load programs can issue only LOAD commands.

· If you issue a DLET, REPL, or ISRT command that references a DB PCB that doesn't have the necessary processing option for that command. The minimum processing options for these calls are D for DLET; R for REPL; and I for ISRT.

· If you issue a DLET, REPL, or ISRT command for a segment to which the program isn't sensitive.

· If you issue a CHKP command if a GSAM/VSAM data set is open for output.

· If you issue a GSAM call with an invalid call function code.

· If you issue an ISRT or DLET command for the index target segment or a segment in the physical database on which the index target is dependent while using an alternate processing sequence.

· If you issue a path replace where the program does not have replace sensitivity, command code N is not specified, and the data for the segment is changed in the I/O area.

· If you issue a call to a GSAM dummy data set. Any call to a GSAM dummy data set is invalid.

Programmer Response: Correct the request, or make the necessary changes in the PCB.

Explanation: There is a BSAM, GSAM, VSAM, or OSAM physical I/O error. When issued from GSAM, this status code means that the error occurred when:

· A data set was accessed.

· The CLOSE SYNAD routine was entered. The error occurred when the last block of records was written prior to closing of the data set.

IMS does not return an AO status code for write errors with BISAM, VSAM, and OSAM.

If your program receives this status code after issuing a call, this call does not cause the database to be stopped.

Programmer Response: Determine whether the error occurred during input or output, and correct the problem. These problems usually require the help of a system programmer or system administrator.

Explanation: A message or CHKP call is invalid because more than 4 parameters (or 5 if parameter count is specified) are in a message call or a CHKP call issued in a transaction-oriented BMP. The following exceptions apply:

· A batch-oriented BMP can issue a CHKP call with more than 4 (or 5) parameters.

· One parameter after the I/O area parameter is allowed in order for the application program to specify a MOD name in an ISRT call. This parameter is counted towards the maximum of 4 (or 5) parameters.

Programmer Response: Correct the call.

Explanation: The length of the data in the program's I/O area is greater than the area reserved for it in the control region. The length of the area reserved is defined by the ACB utility program, DFSUACB0, and printed as part of its output.

Programmer Response: If the program is in error, correct the program. If the program is correct, a larger control region area can be reserved by specifying parameters on the PSBGEN statement of PSBGEN.

Explanation: The total length of the SSAs in the database call is greater than the area reserved for them in the control region. The length of the area reserved is defined by the ACB utility program, DFSUACB0, and printed as part of its output. After this status code is returned, your position in the database is unchanged.

Programmer Response: If the program is in error, correct the program. If the program is correct, increase the PSB SSA space defined in the PSBGEN.

Explanation: IMS ignored a message ISRT call because the logical terminal referenced by the response alternate PCB currently has more than one physical terminal assigned to it for input purposes.

Programmer Response: Ask the master terminal operator to determine (use /DISPLAY ASSIGNMENT LTERM x) which physical terminals (2 or more) refer to this logical terminal. Use the /ASSIGN command to correct the problem.

Explanation: IMS ignored a PURG or ISRT call in a conversational program. Some possible reasons are:

· Issuing a PURG call referencing the I/O PCB or an alternate response PCB. Conversational programs can issue PURG calls only when the PURG call references an alternate PCB that is not an alternate response PCB.

· Issuing a PURG call to send the SPA.

· Issuing an ISRT or a PURG call referencing an alternate PCB that is set for an invalid destination, or a destination that IMS can't determine.

· Issuing an ISRT call referencing an alternate PCB whose destination is a conversational transaction code when the first segment inserted isn't the SPA; or when IMS can't determine whether or not the SPA was the first segment inserted.

Programmer Response: Correct the PURG or ISRT call.

Explanation: You might get the A1 status for the following reasons:

· CHNG call against alternate response PCB when the application has not yet issued a GU.

· CHNG call where MSC routing exit returned return code 4 (use originating system id to route the message back to the original system), but the application has not yet issued a GU.

· CHNG call where MSC routing exit returned return code 8 (return A1 status code).

· The destination name supplied in the I/O area of a CHNG call is invalid.

· The destination name supplied in the I/O area of a CHNG call is valid (the destination is a program and the PCB is not an alternate response PCB), but the transaction is Fast Path exclusive.

· AUTH call parameter list contained an invalid generic CLASS name. No access checking was done.

Programmer Response: Correct the CHNG or AUTH call.

Explanation: The program issued a CHNG call against an invalid PCB. The PCB was invalid for one of these reasons:

· It was not an alternate PCB.

· It was an alternate PCB, but it wasn't modifiable.

· It was being used to process a message and had not completed processing it.

Programmer Response: Check the PCB that was used by the CHNG call and determine which PCB should have been used for the call.

Explanation: The program issued an ISRT or PURG call that referenced a modifiable alternate PCB that did not have its destination set. IMS returns this status code to PURG calls only when the PURG call specified an I/O area as one of the parameters.

Programmer Response: Issue a CHNG call to set the destination of the modifiable alternate PCB, then reissue the ISRT or PURG call.

Explanation: A security violation was detected during processing of an AUTH call, a CHNG call, or a conversational response. Some of the reasons for this status code are:

· Transaction authorization is active and either RACF or a transaction authorization user exit returned a nonzero return code.

· The user is not authorized for access to the RESOURCE name in the class requested in the AUTH call. No 'installation data' is returned.

· No source CNT is available, which may be caused by the application not having issued a GU.

· A program-to-program message switch is being done. In this case, the applicable authorization LTERM is based on the original message, and this authorization does not allow this function to be performed.

Programmer Response: Check the transaction code to make sure it was entered correctly. If it was, check with the person who handles security at your installation.

Explanation: An ISRT or PURG call supplied an invalid parameter list. The call supplied the fourth parameter (the MOD name) but the ISRT or PURG being issued was not for the first segment of an output message.

Programmer Response: Correct the ISRT or PURG call.

Explanation: For a message processing program (MPP or BMP), IMS ignored a message ISRT call because the length of the message segment being inserted exceeds the size specified in the SEGSIZE keyword of the TRANSACT macro. For a Fast Path program (IFP), the length of the output message to a Fast Path terminal exceeds the size specified in the FPBUF parm of the TERMINAL macro.

Programmer Response: Correct the output message segment.

Explanation: IMS ignored a message ISRT call because the number of message segments inserted exceeds the number specified in the SEGNO keyword of the TRANSACT macro.

Programmer Response: Check the output messages and correct them.

Explanation: IMS ignored an ISRT call because:

· An ISRT call to a response alternate PCB must not follow an ISRT call to the I/O PCB.

· An ISRT call to the I/O PCB must not follow an ISRT call to a response alternate PCB.

Programmer Response: Correct the ISRT call.

Explanation: IMS ignored the ISRT call because:

· The ISRT call referenced an alternate response PCB defined as SAMETRM=YES, but the PCB represented a logical terminal that isn't part of the originating physical terminal. An alternate response PCB defined as SAMETRM=YES must represent the same physical terminal as the physical terminal associated with the originating logical terminal.

· The originating terminal is in response mode and the response alternate PCB is not associated with that logical terminal.

IMS does not return this status code if the program makes either of these errors while communicating with a terminal in a remote IMS system through MSC.

Programmer Response: Determine whether the application program is in error, the output logical terminal has been incorrectly reassigned (using the /ASSIGN command), or if SAMETRM=YES should not have been specified for the response alternate PCB.

Explanation: The request was not completed because it required access to unavailable data.

Only the updates done for the current request, prior to the time it encountered the unavailable data, are backed out. The state of the database is as it was before the failing request was issued. If the request was REPL or DLET, the PCB position was unchanged. If the request was a get type or ISRT request, the PCB position is unpredictable.

For a DEDB, this status code may be returned if no updates have been made since the last commit point. If updates have been made since the last commit, a BB status code is returned instead.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: This is an information-only status code.

Explanation: Same as BA except all database updates that the program made since the last commit point are backed out, and all nonexpress messages sent since the last commit point are cancelled. The PCB position for all PCBs is at the start of the database.

For a DEDB, this status code may be returned if updates have been made since the last commit point.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: This is an information-only status code.

Explanation: The response from an INIT STATUS GROUPB call was not completed because it required access to unavailable data.

All database resources to the last commit point are backed out, with the exception of GSAM and DB2. All output messages are backed out to the last commit point. Input messages are requeued.

Programmer Response: This is an information-only status code.

Explanation: All of the databases in the PSB are unavailable, or there are no database PCBs in the PSB.

Each PCB (excluding GSAM) received an NA status code as the result of the INQY DBQUERY call.

Programmer Response: This is an information-only status code.

Explanation: At least one of the databases included in the PSB is unavailable or has limited availability.

At least one PCB received an NA or NU status code as the result of processing the INQY DBQUERY call.

Programmer Response: This is an information-only status code.

Explanation: The program issued a CMD call with an invalid command verb, or the command verb does not apply to the IMS system that the program's running in. IMS does not return any command responses.

Programmer Response: Correct the command in the CMD call.

Explanation: The command entered in the CMD call is not allowed from an AOI program. IMS does not return any command responses.

Programmer Response: Correct the command. For a list of the commands that an AOI program can issue, see "Automated Operator Programming," in IMS/ESA Customization Guide: Data Communication.

Explanation: IMS has executed the command and returned one or more command responses.

Programmer Response: Your program should issue GCMD calls as necessary to retrieve the responses.

Explanation: The command that was entered on the CMD call violates security, or the application program isn't authorized to issue CMD calls. IMS does not execute the command or return any command responses.

Programmer Response: Correct the command. If necessary, check with the person in charge of security at your installation to find out why your program is restricted from using that command.

Explanation: IMS rescheduled the message that this GU call retrieved since the last CMD call. The program had not reached a commit point when the message was rescheduled.

Programmer Response: This is an information-only status code.

Explanation: This status code can be returned only to programs that are authorized to issue AOI commands (CMD calls). The message being returned on the GU call was received by IMS before the start of this IMS execution. CF can be received on a CHKP call whan an I/O area is specified for an MPP or message-oriented BMP. This occurs when a CHKP call issues an internal GU call.

Programmer Response: This is an information-only status code.

Explanation: The message retrieved by this GU originated from an AOI user exit.

Programmer Response: This is an information-only status code.

Explanation: IMS ignored the CMD call just issued because the AOI command interface detected a system error and was unable to process the command. IMS processing continues.

Programmer Response: Reissue the command.

Explanation: CI is a combination of CE and CF. The message retrieved by this GU was scheduled for transmission before IMS was last started. The message was rescheduled, but the program hadn't reached a commit point.

Programmer Response: This is an information-only status code.

Explanation: CJ is a combination of CE and CG. The message retrieved by this GU was scheduled for transmission before IMS was last started. The message originated from an AOI user exit.

Programmer Response: This is an information-only status code.

Explanation: CK is a combination of CF and CG. The message retrieved with this GU originated from an AOI user exit. The message was scheduled for transmission before IMS was last started.

Programmer Response: This is an information-only status code.

Explanation: CL is a combination of CE, CF, and CG. Please see the explanations of those codes.

Programmer Response: This is an information-only status code.

Explanation: The command that was entered on the CMD call has been executed and completed, but resulted in an exception response that could not be built because of an insufficient amount of general work area (WKAP).

Programmer Response: Increase WKAP if you want retrieval of the response.

Explanation: The PSBIOASZ is defined for less than the minimum required for CMD calls (132 bytes).

Programmer Response: Redefine PSBIOASZ for 132 bytes.

Explanation: The program issued a DLET or REPL that tried to modify the key field in the segment or, when using field level sensitivity, a REPL call tried to modify a field that had REPL=NO specified on the SENFLD STMT in the PSB. You cannot change a segment's key field.

Programmer Response: Correct the request.

Explanation: The program issued a DLET or REPL call that was rejected because the segment was not currently in hold status. Some possible reasons for this status code are:

· The segment had not been previously retrieved with a get hold call.

· The segment was already deleted using this PCB. After one get hold call, multiple REPL calls or a DLET call following a REPL call are valid but multiple DLET calls are not. valid but multiple DLET calls are not.

· The segment was obtained using a secondary index as the processing sequence. A subsequent DLET or REPL call using either this PCB or another PCB within the PSB caused the current secondary index entry for this PCB to be deleted.

· A checkpoint call was issued following the get hold call and preceding the REPL or DLET call.

Programmer Response: Correct the program so that the segment is in hold status when a DLET or REPL is issued.

Explanation: The program issued a DLET that violates the delete rule for that segment.

Programmer Response: Check the program to see whether or not the program should delete that segment; if it should, check with your DBA (or the equivalent specialist at your installation) to find out what delete rule has been specified for that segment.

Explanation: IMS returns this status code when the program reaches a commit point and an arithmetic overflow in an MSDB has occurred during that commit interval (since the last commit point, or, if the program had not reached a commit point, since the program began processing). You can receive this status code on a SYNC call, a CHKP call, or a GU call to the message queue, depending on your program. The overflow occurred after the program issued a FLD/CHANGE call or a REPL call for the MSDB. When this happens, IMS issues an internal ROLB call to eliminate the changes that the program has made since the last commit point. All database positioning is lost.

Programmer Response: Reprocess the transaction.

Explanation: The program issued a request that is not valid for the segment type.

Programmer Response: Correct the request.

Explanation: A nonmessage driven BMP reached a deadlock when IMS tried to get DEDB or MSDB resources (either DEDB UOWs or overflow latches) for the program. Or, a mixed mode BMP reached a deadlock on any resource, either Fast Path or full function. IMS eliminates all database updates that the program has made since the last SYNC call, CHKP request, or SYMCHKP command (or since the program started processing, if the program hasn't issued a SYNC call or CHKP request). All database positioning is lost, unless you specified the P processing option in the PCB.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: Start processing from the last commit point. If you reach a deadlock again (and you usually won't), terminate the program.

Explanation: IMS returns this status code anytime a program issues a FLD call that receives a nonblank status code in the FSA.

Programmer Response: See "Fast Path Data Areas" in IMS/ESA Application Programming: DL/I Calls for an explanation of FSA status codes and correct the FLD call.

Explanation: A program issued an ISRT (add) call against an MSDB that has no free space. If IMS determines that there is no free space when the program issues the ISRT call, the program receives the FF status code for that call. IMS may not determine this until the program reaches the next commit point. In this case, IMS returns FF when the program issues a GU call to the message queue, a SYNC call, or a CHKP call, depending on which call caused the commit point.

Programmer Response: To avoid this situation, you can specify more space for the MSDB at the next system start (cold start or normal restart).

Explanation: FG is a combination of FE and FW. A batch-oriented BMP issued a FLD call that received a nonblank status code in the FSA, and the program has used up its normal buffer allocation.

Programmer Response: Check the FSA status code and correct the FLD call, then issue SYNC or CHKP calls in the program more frequently. One way to handle this status code is to branch to an error routine that causes the program to issue SYNC or CHKP calls more frequently when it receives this status code.

Explanation: A DEDB area was inaccessible to the requested service when the program issued a database request or when the program reached a commit point.

If IMS returns this status code on a call that caused a commit point to occur (a SYNC call, a message GU, a CHKP request, or SYMCHKP command), IMS issues an internal ROLB call to eliminate the program's database updates and message output created since the last commit point.

If your program is accessing a DEDB in a data sharing environment, and if the authorization fails when your program issues its first DL/I call to the DEDB, Fast Path returned this status code. Fast Path also notified the master terminal operator of the authorization failure. Your position in the database is before the first root in the next area. A GN will get the next available record (unless that one is also inaccessible).

Note: If a program has access to an area through a PCB with PROCOPT=H and another PCB without PROCOPT=H, it is possible that only calls to the PCB with PROCOPT=H will receive the FH status code. This is because the area is accessible to IMS, but the required HSSP (high-speed sequential processing) setup could not be established. Message DFS0533A explains the reason for this occurrence and is sent to the job log. This status code is also returned if the PROCOPT for one PCB is more restrictive than the PROCOPT of a different PCB in the same PSB. Position is set to the beginning of the next accessible area.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: If the data in the area is important, contact the DBA. If the data in the area is unimportant, the program should roll back the changes. Your program can continue processing with the next available area.

If the status code is related to an HSSP setup problem, fix the error as described in the message DFS0533A in the job log.

Explanation: The program's I/O area is not at a storage address that the program can access.

Programmer Response: Correct the program.

Explanation: The application issued a request for which the randomizer returned a return code of 4.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: The database position has not changed. The application program must determine subsequent processing.

Explanation: The program issued a FLD call that contains a field name in the FSA that is not defined in the DBD. IMS doesn't continue processing the FLD call or any of the FSAs in the FLD call. IMS returns an FN status code in this situation even if an earlier FSA in the same FLD call earned an FE status code.

Programmer Response: Issue a ROLB call to remove the effects of the incorrect FLD call and correct the FLD call.

Explanation: The I/O area referenced by a REPL, ISRT or FLD/CHANGE call to an MSDB contains an invalid packed decimal or hexadecimal field.

Programmer Response: Correct the data in the I/O area.

Explanation: One of the following situations exists:

· A batch-oriented BMP issued a database request that forced the system to go beyond the buffer limit specified for the region.

· A batch-oriented BMP received a GC status code in a PCB with PROCOPT=H. Another commit process was required before using the PCB again.

IMS eliminates all database changes made by the program since the last SYNC call, CHKP request, or SYMCHKP command the program issued (or since the program started processing if the program hasn't issued any SYNC calls, CHKP requests, or SYMCHKP commands.) All database positions for PCBs not referring to a DEDB with PROCOPT=P or H active are lost. If the PCB referred to a DEDB with PROCOPT=P or H active, the position is set to the position valid after the last commit process, or the start of the valid range if there was no commit process.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: Either terminate the program and restart it with a larger buffer allocation, or provide a routine that causes frequent commit points. If PROCOPT=H is used, make sure that a commit point is requested after a GC code has been returned.

Explanation: For a root segment or direct dependent segment, this status code is returned only to BMPs. For a sequential dependent segment, this status code can be returned to either a BMP or a message-driven program:

· A BMP issued an ISRT request for a root segment, a direct dependent segment, or a sequential dependent segment, but IMS could not get enough space in either the root addressable or sequential dependent part of the DEDB area to insert the new segment:
If IMS returns this status code on an ISRT request for a root segment, a direct dependent segment, or a sequential dependent segment, the problem is with the root addressable portion of the area, the independent overflow area, or the sequential dependent area.
If IMS returns this status code when the program issues a SYNC call, CHKP request, or SYMCHKP command, the problem is with the sequential dependent part of the area.
In either case, IMS eliminates all of the database changes the program has made since the last commit point (or since the program started processing, if the program hasn't reached a commit point).

· A message-driven program issued an ISRT request for a sequential dependent segment, and the sequential dependent part is full.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: Continue with other processing, and report the problem to the system programmer.

Explanation: The Fast Path program issued a call to a Fast Path database that included too many SSAs. A call to a DEDB may include up to 15 SSAs. A call to an MSDB may include 1 SSA.

Programmer Response: Correct the call.

Explanation: At least one of the verify operations in a FLD call issued in a batch-oriented BMP failed when the program reached a commit point. IMS eliminates the database updates the program has made since it issued the last SYNC or CHKP call (or if the program hasn't issued a SYNC or CHKP call, since the program started processing). All database positioning is lost.

Programmer Response: Reprocess the transaction or terminate the program.

Explanation: A BMP has used all buffers that are allocated for normal use, or all buffers have been modified. IMS returns this status code to warn you that you may be running out of buffer space. An FR status code may be imminent.

If you have been processing a DEDB, you get FW for requests that change data.

If you have been processing a MSDB, you get FW for all calls that change data and for GH calls.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: You can supply an error-handling routine, triggered by the FW status code, that will cause your program to issue SYNC calls, CHKP requests, or SYMCHKP commands as soon as an FW status code is returned to your program. This reduces the total buffer requirement. To avoid receiving the FW status code, issue SYNC or CHKP calls more frequently.

Explanation: In trying to satisfy an unqualified GN or GNP, IMS crossed a hierarchic boundary into a higher level.

If IMS returns GA after a STAT request, it means that the request just issued retrieved the total statistics for all the VSAM buffer subpools.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: This status code is an information-only status code. What you do next depends on your program.

Explanation: In trying to satisfy a GN, DL/I reached the end of the database or, if you used a SETR statement, the end of the current range. In this situation, the SSA for the call or qualification for the command specified data beyond the last occurrence, and the search was not limited to the presence of a known or expected segment occurrence.

For example, a GN was specified for a key greater than a particular value, rather than a GU specifying a key value beyond the highest value.

A GB status code can be returned for:

· An unqualified GN call.

· A qualified GN call without a maximum key (if no data is returned to the I/O area).

In contrast, a GE status code, instead of a GB status code, can be returned for:

· A GU call.

· A qualified GN call without a maximum key (if data is returned to the I/O area).

· A qualified GN call with a maximum key.

IMS also returns this status code when it has closed a GSAM data set. The assumed position for a subsequent request for a GSAM or full-function database is the beginning of the database, or if a SETR statement was used for a DEDB database, the beginning of the current range.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: User determined.

Explanation: An attempt was made to cross a unit-of-work (UOW) boundary. For a batch-oriented BMP PCB with PROCOPT=H or PROCOPT=P, there was at least one call on the referenced PCB that changed position in the database since the last commit process or after the program began executing. IMS did not retrieve or insert a segment. Position is before the first segment of the following UOW.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: User determined. However, if the GC status code results from a call that referred to a PCB with PROCOPT=H, the program has to cause a commit process before any other call can be done to that PCB. Failure to do so results in an FR status code.

Explanation: The program issued an ISRT that was not qualified for all levels above the level of the segment being inserted. For at least one of the levels for which no qualification was specified, a prior request using this PCB established valid position on a segment. That position is no longer valid for one of these reasons:

· The segment has been deleted by a DLET using a different DB PCB.

· The segment was retrieved using an alternate processing sequence, and a REPL or DLET for this DB PCB caused the index for the existing position to be deleted.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: User-determined.

Explanation: For call-level programs: IMS returns this status code when:

· DL/I is unable to find a segment that satisfies the segment search argument described in a get call.

· For an ISRT call, DL/I can't find one of the parents of the segment being inserted.

· For an ISRT call, DL/I was requested to insert a root segment outside of the accessible range determined by a SETR statement.

· The program issued a STAT call for OSAM buffer pool statistics, but the buffer pool doesn't exist.

· The program issued a STAT call for VSAM buffer subpool statistics, but the subpools don't exist.

· A nonmessage driven BMP issued an FLD call to an MSDB segment. After the FLD call but before a commit point, the MSDB segment was deleted. GE can be returned for this reason after either a SYNC or a CHKP call.

For command-level programs:

· DL/I is unable to find a segment that satisfies the segment described in a get command.

· For an ISRT command, DL/I can't find one of the parents of the segment you're inserting.

· The program issued a STAT command for ISAM/OSAM buffer pool statistics, but the buffer pool doesn't exist.

· The program issued a STAT command for VSAM buffer subpool statistics, but the subpools don't exist.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: The action you take depends on your program.

Note: When a GNP call for a DEDB sequential dependent segment results in a GE status code, the I/O area contains a length indication of 10 bytes and the original position of the deleted portion of the sequential dependent part. Position is at the end of the sequential dependent chain.

Explanation:
For call-level programs: DL/I returns this status code if the segment being retrieved contains an invalid pointer and the application program has a processing option of GOT or GON. (Processing options are explained under PROCOPT in the discussion of program specification block generation in IMS/ESA Utilities Reference.) This can occur when update activity in the database is going on concurrently with your program's processing. The PCB key feedback length and area will be based on the last segment that satisfied the call. Your position is at the beginning of the database.

For command-level programs: DL/I returns this status code if the segment being retrieved contains an invalid pointer and the application program has a processing option of GON or GOT. (Processing options are explained under PROCOPT in the discussion of program specification block generation in IMS/ESA Utilities Reference.) This can occur when update activity in the database is going on concurrently with your program's processing. If your request specified KEYFEEDBACK, the DIBKFBL will contain the length of the key of the last segment that satisfied the command. Your position is at the beginning of the database.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: Continue processing with another segment or terminate the program. The request that resulted in the GG status code may be successful if you issue it again.

Explanation: DL/I has returned a different segment type at the same hierarchic level for an unqualified GN or GNP.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: This is an information-only status code.

Explanation: The program issued a LOG request that contained an invalid log code for user log records. The log code in a LOG request must be equal to or greater than X'A0'.

DL/I returns GL on a DEQ request when the first byte of the I/O area referenced in the request did not contain a valid DEQ class (A-J).

Programmer Response: Correct the log code, which is the first byte of the log message. If the program received this status code for a DEQ request, check the DEQ class code in the I/O area.

Explanation: The program issued a GNP when there is no parentage established, or the segment level specified in the GNP is not lower than the level of the established parent.

Programmer Response: Make sure you have established parentage before issuing GNP, and check the segment level specified by the GNP.

Explanation: The program issued an ISRT that tried to insert a segment that already exists in the database. Current position after an II status code is just before the duplicate of the segment you tried to insert. Some of the reasons for receiving this status code are:

· A segment with an equal physical twin sequence field already exists for the parent.

· A segment with an equal logical twin sequence already exists for the parent.

· The logical parent has a logical child pointer, the logical child doesn't have a logical twin pointer, and the segment being inserted is the second logical child for that logical parent.

· The segment type doesn't have physical twin forward pointers and the segment being inserted is the second segment of this type for that parent, or it is the second HDAM root for one anchor point.

· The segment being inserted is in an inverted structure. (The immediate parent of this segment in the logical structure is actually its physical child in the physical structure.)

· A physically-paired logical child segment already exists with a sequence field equal to that of the segment you're inserting. For example, the segment could have been inserted with no duplication but when an attempt was made to position for the insert of its physical pair, it was found to have a duplicate key to an existing twin segment.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: User determined.

Explanation: The program issued an ISRT that violated the insert rule for that segment. Some of the reasons that IMS returns this status code are:

· The program tried to insert the logical child and logical parent, and the insert rule for the logical parent is physical and the logical parent does not exist.

· The program tried to insert the logical child and the logical parent, and the insert rule is logical or virtual and the logical parent doesn't exist. In the I/O area, the key of the logical parent doesn't match the corresponding key in the concatenated key in the logical child.

· The program tried to insert a logical child, and the insert rule of the logical parent is virtual and the logical parent exists. In the I/O area, the key in the logical parent segment doesn't match the corresponding key in the concatenated key in the logical child.

· The program tried to insert a physically paired segment, where both sides of the physical pair are the same segment type and the physical and logical parent are the same occurrence.

· The program issued an ISRT to a GSAM database after receiving an AI or AO status code.

Programmer Response: Correct the ISRT, or the program.

Explanation: The segment that the program tried to load already exists in the database. Other possible causes are:

· A segment with an equal physical twin sequence field already exists for the parent.

· A segment type doesn't have a physical twin forward pointer, and the segment being inserted is either the second segment of this segment type for the parent or the second HDAM root for one anchor point.

· An application program inserted a key of X'FF...FF' into a HISAM or HIDAM database.

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Programmer Response: Correct the ISRT call or LOAD command, or find out if the load sequence is incorrect. Check with the DBA or the equivalent specialist at your installation.

Explanation: The key field of the segment being loaded is out of sequence.

Programmer Response: Check the segment and determine where it should be loaded.

Explanation: No parent has been loaded for the segment being loaded.

Programmer Response: Check the sequence of segments that have been loaded and determine where the parent should have been loaded.

Explanation: The sequence of sibling segments being loaded is not the same as the sequence that is defined in the DBD.

Programmer Response: Check the sequence of the segments that are being loaded and correct.

Explanation: IMS ignored a message insert (ISRT) call because the logical terminal referenced by the message requeuer segment is invalid.

Programmer Response: Verify the LTERM name supplied in the message requeuer segment.

Explanation: The INIT call with DBQUERY in the I/O area or the QUERY command was issued, and at least one of the databases that could be accessed using this PCB was not available.

A request made using this PCB will probably result in a BA status code if the INIT 'STATUS GROUPA' has been issued or in a DFS3303I message and 3303 pseudo abend if it has not. An exception is when the database is not available because dynamic allocation failed. In this case, a request results in an AI (unable to open) status code.

Programmer Response: This is an information-only status code.

Explanation: Indexing maintenance issued a DL/I call, and the segment has not been found. This status code is included in message DFS0840I. The system console receives message DFS0840I, "INDEX ERROR (dbdname) NE (first 45 bytes of key)," and the application program receives a blank status code.

An application program could have processed a secondary index as a database and thus deleted some of the secondary index entries. Subsequently, when a source segment is deleted, the secondary index for the source statement might not be present. For this reason, when the application program deletes a source segment and the index entry is not present, the DFS0840I message is sent to the system console, but a blank status code is returned to the application program.

Programmer Response: Determine whether the secondary index has been processed as a database and, as a result, the key included in the DFS0840I message was deleted. If this is not the case, check the cause for the index inconsistency with the database and correct it.

Explanation: There is a duplicate segment in a unique secondary index. While IMS was inserting or replacing a source segment for a secondary index defined with a unique sequence field, the insertion of the secondary index segment was attempted but was unsuccessful because an index segment with the same key was found. One possible cause for a duplicate segment in the index is that the index DBD incorrectly specified a unique key value--secondary index only.

In an online application program, the call is backed out and the program receives an NI status code.

For a batch program that doesn't log to the IMS DASD log, IMS abnormally terminates the program with a U0828 abend. You should run batch backout.

For a CICS local DL/I or shared database application program, CICS abends the transaction and backs out all updates made by that logical unit of work (LUW).

Programmer Response: The response is determined by the user. If duplicate secondary index entries occur, specify the index as nonunique, and provide an overflow entry-sequenced data set.

Explanation: A BSAM or VSAM physical I/O error occurred during a database request issued by the index maintenance function.

For an online program, all updates made for the call are backed out and the application receives the NO status code. For a batch program that does not log to the IMS DASD log, IMS abnormally terminates the program with an 826 abend. Run batch backout. For CICS local DL/I or shared database programs, CICS abends the transaction and backs out all the updates made by the logical unit of work (LUW).

Programmer Response: See accompanying messages giving details of the error. In a batch environment, execute batch backout.

Explanation: An ISRT, DLET or REPL request using this PCB may result in a BA status code if the INIT STATUS GROUPA call or QUERY command has been issued or in a DFS3303I message or 3303 pseudo abend if it has not. If the unavailable database is only required for delete processing, it is possible that the ISRT and REPL requests can be processed.

Programmer Response: This is an information-only status code.

Explanation: An MPP or transaction-oriented BMP issued a successful CHKP call, but the message GU call issued internally by the CHKP call was unsuccessful. There are no more messages in the queue for the program.

Programmer Response: This is an information-only status code.

Explanation: The program issued a message GN, but there are no more segments for this message.

Programmer Response: Process the message.

Explanation: The program issued a message GN call before issuing a GU to the message queue. In message-driven Fast Path programs, this code applies to message calls only. This code also applies to GCMD calls in AOI programs. It means that the program issued a GCMD call before issuing a CMD call. This code is also returned when a program issues a ROLB, specifying the I/O area parameter, without having issued a successful message GU call during that commit interval.

Programmer Response: Correct the program by either:

· Issuing a GU call before the GN

· Issuing a CMD call before the GCMD

· Issuing a GU call before the ROLB

Explanation: The length of the segment is less than 5 characters. The minimum length allowed is the length of the message text plus four control characters.

Programmer Response: Correct the segment.

Explanation: There has been a terminal symbolic error. The output logical terminal name or transaction code is unknown to IMS. Some reasons for receiving this status code are:

· The program tried to insert an alternate response PCB receiving a QC status code for a GU.

· SMB or CNT could not be found.

· The program issued an ISRT call without first issuing a GU.

· The logical terminal name or transaction code specified is Fast Path exclusive and not available to this program.

· The program issued an ISRT call for a segment shorter than 5 bytes.

· The program issued an ISRT call for an SPA shorter than 6 bytes.

· The logical terminal name or transaction code has leading blanks, instead of being left-justified.

Programmer Response: Check the logical terminal name or transaction code and correct it.

Explanation: The token does not match a token for any outstanding SETS requests or the request was issued for a database PCB that did not get a BA status on the previous request.

Programmer Response: The outstanding SETS request may have been cancelled by a commit process, or an error exists in the use of the token.

Explanation: The ROLS request was rejected because the PSB contains access to a DEDB, MSDB, or GSAM organization or has access to an attached subsystem.

Programmer Response: The ROLS request is invalid in this environment. The program must either remove the use of the database organization that is preventing the use of the ROLS call or not use the ROLS call.

Explanation: The program issued a REPL that violated the replace rule for that segment.

Programmer Response: Correct the REPL, or check with the DBA or the equivalent specialist at your installation.

Explanation: On a SETS request, IMS was not able to obtain the storage space for the data in the I/O area.

Programmer Response: A larger region size is required for the job step.

Explanation: The maximum number of levels, nine, of SETS were already specified, and this request is attempting to set the tenth.

Programmer Response: Correct the program.

Explanation: The SETS request was rejected because the PSB contains an access to a DEDB, MSDB, or GSAM organization or has accessed an attached subsystem.

Programmer Response: The SETS request is invalid in this environment. The program must either remove the use of the database organization that is preventing the use of the SETS request, or the program must not use the SETS request.

Explanation: This status code applies to CICS online command-level programs only, and is returned following a scheduling request. It means that the PSB named in the request is not in the PSB directory.

Programmer Response: Correct the name of the PSB in the scheduling request, or add the PSB name to the PSB directory.

Explanation: This status code applies to CICS online command-level programs only, and is returned following a scheduling request. It means that you have already scheduled a PSB.

Programmer Response: Correct your program so that you terminate a PSB before scheduling another. If you want to reschedule a PSB, you must have already terminated the PSB.

Explanation: This status code applies to CICS online command-level programs only, and is returned following a scheduling request. It means that the PSB could not be scheduled; an initialization error occurred.

Programmer Response: See your system programmer or DBA. For a list of possible causes for the PSB initialization error, see the description under PSBFAIL under "Invalid Request Conditions" in the chapter "CICS-DL/I Interface Return Codes" in IMS/ESA Application Programming: DL/I Calls.

Explanation: This status code applies to CICS online command-level programs only, and is returned following a terminate request. It means that the program issued a terminate request when there was no PSB scheduled.

Programmer Response: This is an information-only status code. If you only wanted to terminate a PSB, you should continue with processing. If you also wanted to cause a sync point, you should issue a SYNCPOINT command. (No sync point was caused by the unsuccessful terminate request.)

This status code is returned to the application program that issued the EXEC DLI command rather than causing an abnormal termination.

Explanation: This status code applies to CICS online command-level programs only, and is returned following a database request, or a statistics request. It means that the program attempted to access the database before scheduling a PSB.

Programmer Response: Correct your program, and schedule a PSB before accessing the database.

Explanation: This status code applies to command-level programs only, and is returned after an ISRT command. It means that the ISRT command defined an invalid path to the segment. Data must be transferred for all segments between the first segment named and the last one named.

Programmer Response: Correct the ISRT command, specifying a FROM option for each segment to be transferred.

Explanation: This status code applies to CICS online command-level programs only, and can be returned after any command used by a CICS online program. It means that DL/I is not active.

Programmer Response: Contact your DBA. CICS must be reinitialized with DL/I defined as active in the SIT.

Explanation: This status code applies to CICS online command-level programs only, and is returned after a scheduling request. It means that there is a conflict in scheduling intent. (This cannot occur if program isolation has been specified.)

Programmer Response: Specify program isolation in the SIT. If program isolation has not been specified, wait until the PSB is no longer in use, and reschedule it.

Explanation: This status code applies to command-level programs only, and can be returned after any of the commands. It means that there is an invalid SDIB. An initialization call was not made, or the system's DIB (not the application program's DIB) was overlaid.

Programmer Response: Check your program to make sure that you did not use an entry statement, as you would in a call-level batch program. Also make sure that there are no addressing errors in your program that would cause an overlay.

Explanation: This status code applies to command-level programs only, and is returned following a REPL command. It means that there has been a path-replace error. The segments to be replaced are compared to the previous get command, and either a segment is named to be replaced that was not retrieved by the get command, or data had not been transferred (no INTO option) for this segment on the get command, or the attributes of the data to be transferred don't match the data in the database.

Programmer Response: Correct the program.

Explanation: This status code applies to command-level programs only, and is returned following any of the database commands, a LOAD command, or a statistics request. It means that the number of the PCB specified in the USING option is higher than the number of PCBs in the PSB being used; or that there is an invalid processing option. For example, the program tried to issue a LOAD command without having the L processing option specified in its PSB.

Programmer Response: Check the PSB and correct your program.

Explanation: This status code is returned when a program running in local DL/I tries to use an IOPCB.

Programmer Response: Correct the program.

Explanation: This status code means that the CICS XDLIPRE exit routine returned X'04' in register 15 because the routine determined that the immediately preceding DL/I request should not be executed.

Programmer Response: Contact the CICS system programmer.

Explanation: This status code applies to CICS online command-level programs only, and is returned following a database or statistics request. It means that the database was not open when the request was issued.

Programmer Response: Contact your database administrator or system programmer. The database can be checked and opened via operator commands.

Explanation: This status code applies to CICS online command-level programs only, and is returned following a database or statistics request. It means that the length of the retrieved segment is greater than 64 bytes.

Programmer Response: Contact your database administrator or system programmer--the database definition may require modification.

Explanation: This status code is returned for batch programs only. A checkpoint record was written to the UCF (8) journal data set. During the processing of an HD reorganization, a reload, or an initial load program under the supervision of the Utility Control Facility (UCF), a checkpoint record was written to the UCF journal data set. IMS returns this status code to indicate that the last ISRT call was correct and the initial load program may continue or it may perform a checkpointing procedure before continuing.

Programmer Response: This is an information-only status code.

Explanation: This status code is returned for batch programs only. Your initial load program is being restarted under UCF (8). The program terminated while executing under UCF. The job was resubmitted with a restart request.

Programmer Response: The program has to get itself back in step with database loading. The program uses the I/O area and the DB PCB key feedback area to do this.

Explanation: This status code is returned for batch programs only. The initial load program is about to stop processing. While processing an HD reorganization reload or user initial load program under the supervision of UCF (8), the operator replied to the WTOR from UCB and requested the current function to terminate. The last ISRT call was processed.

Programmer Response: The initial load program should checkpoint its data sets and return with a nonzero value in register 15.

Explanation: This status code is returned for batch programs only. A checkpoint record was written and processing stopped. This is a combination of UC and US status codes.

Programmer Response: See the descriptions of UC and US status codes.

Explanation: The program tried to insert or replace a variable-length segment that is too long. The length of the segment must be equal to or less than the maximum length specified in the DBD. The length must be long enough to include the entire reference field; if the segment is a logical child, it must include the entire concatenated key of the logical parent and all sequence fields for the paired segment. The program tried to delete a variable-length segment. The copy of this segment in the user's I/O area contains an invalid length field.

IMS also returns this status code when an invalid record length is specified in a GSAM call.

Programmer Response: Correct the program.

Explanation: This status code applies to command-level programs only, and is returned following a database or LOAD command. It means that the segment length is missing or invalid. The segment length must be a positive integer. For variable-length segments, it is the maximum size acceptable to the program's I/O area.

Programmer Response: Check that the program translated and compiled correctly. The value of any segment length in a path command should not exceed 32K bytes, and the sum of the lengths should not exceed 64K bytes.

Explanation: This status code applies to command-level programs only, and is returned following a get or INSERT command. It means that the field length is missing or invalid. The field length must be a positive integer, and must be specified for each field in a WHERE option.

Programmer Response: Correct the program.

Explanation: This status code applies to command-level programs only, and is returned following any of the database commands or a LOAD command. It means that the length of a variable-length segment is invalid. The LL field as provided by the program on an ISRT or REPL command, or as received in the I/O area on a Get command, exceeds the value of SEGLENGTH.

Programmer Response: Correct the program.

Explanation: This status code applies to command-level programs only, and is returned following a Get, REPLACE, or INSERT command. It means the offset is invalid. The offset must be a positive integer and not greater than the segment length. than the segment length.

Programmer Response: Correct the program.

Explanation: This status code applies to command-level programs only, and is returned following a Get or ISRT command using the KEYS option. It means that the concatenated key length is missing or invalid. The length of the concatenated key must be a positive integer.

Programmer Response: Correct the program.

Explanation: This status code applies to command-level programs only, and is returned following a STATISTICS command. It means that the statistics area length is either too small or invalid. The length must be a positive integer, and must be at least 72 bytes for unformatted statistics, 120 bytes for summary statistics, and 360 bytes for formatted statistics.

Programmer Response: Correct the program.

Explanation: The program tried to continue processing the conversation by passing the SPA to another program through a program-to-program message switch after already responding to the terminal.

Programmer Response: If a response has been sent, the SPA should be returned to IMS. Correct the program.

Explanation: The program has passed the SPA to another program but is trying to respond to the originating terminal.

Programmer Response: No response is allowed by a program that is passed control of the program through a program-to-program message switch.

Explanation: The program inserted a message that has some bits in the Z1 field set. The Z1 field is reserved for IMS.

Programmer Response: Correct the program to prevent it from setting those bits.

Explanation: IMS is terminating by a CHECKPOINT FREEZE or DUMPQ. IMS returns this code to a BMP that has issued a CHKP or SYNC call. If it is a transaction-oriented BMP, IMS does not return a message.

IMS also returns XD when a batch program issues a SYNC call.

Programmer Response: Terminate the program immediately. IMS will terminate the program abnormally if the program issues another call.

Explanation: A program tried to insert a SPA to an alternate express PCB.

Programmer Response: Regenerate the PSB and remove the EXPRESS=YES option from the PCB, or define another PCB that is not express to be used in the ISRT call.

Explanation: IMS is ignoring the ISRT call for the SPA because the specified alternate PCB had its destination set to a logical terminal but was not defined as ALTRESP=YES during PSB generation.

MSC directed routing does not support a program-to-program switch between conversational transactions.

Programmer Response: Correct the application program or change the PSB generation for that alternate PCB to specify ALTRESP=YES.

Explanation: IMS ignored the ISRT call because the current conversation requires fixed-length SPAs and the ISRT call was to a program with a different length or variable-length SPA.

Programmer Response: Correct the program or the SPA definitions.

Explanation: An error occurred during GSAM initialization or during GSAM call processing. If this status code is in the GSAM PCB before the application issued the first call, the error was detected during initialization. Possible causes are:

· Insufficient space

· Invalid DBD

· Invalid block size

· Invalid option

· Internal GSAM error

Programmer Response: A subsequent GSAM call will result in an abnormal termination of the program. The program should terminate.

Explanation: After a ROLB call, an I/O error occurred while IMS was reading the SPA from the message queue data set.

Programmer Response: Terminate the conversation.

Explanation: The first ISRT call to an alternate PCB whose destination is a conversational transaction code is not for the SPA. The SPA must be inserted with the first ISRT call.

Programmer Response: Insert the SPA, then reinsert the message segment.

Explanation: The program modified the first 6 bytes of the SPA; the SPA is now invalid.

Programmer Response: Correct the program and restore the original bytes.

Explanation: The program issued an ISRT call to pass the SPA to a nonconversational transaction code. It did this by referencing a PCB whose destination was set for the nonconversational transaction code. You can send the SPA only to transaction codes defined as conversational.

Programmer Response: Correct the ISRT call. Send only data segments.

Explanation: The program issued more than one ISRT call to send the SPA to a PCB whose destination is a transaction code.

Programmer Response: Only one SPA is allowed per message. Correct the program.

Explanation: An invalid transaction code name was inserted into the SPA.

Programmer Response: Correct the program to set the proper transaction code name.

Explanation: The length of the SPA is incorrect. The program modified the first 6 bytes.

Programmer Response: Correct the SPA and the program.

Explanation: There was a system or I/O error in attempting to queue a SPA on a transaction code PCB.

Programmer Response: Terminate the conversation.

Explanation: The program tried to insert the SPA for a program-to-program switch and the length of the SPA in the destination program is greater than the maximum SPA length defined by the SPAREA macro at IMS generation.

Programmer Response: Contact your IMS system programmer to change the size of the SPA defined in the destination program or to increase the maximum SPA length defined for the system.

Blanks

Explanation: The call was completed.

Programmer Response: Proceed with processing.

File Status Codes (or) COBOL Abend Codes

noreply@blogger.com (M siva raman) — Fri, 08 Apr 2011 17:06:00 +0000

ERROR REASON

CODE

00                    Operation completed successfully
02                    Duplicate Key was found
04                    Invalid fixed length record
05                    The file was created when opened - Successful Completion
07                    CLOSE with REEL or NO REWIND executed for non tape dataset.
10                    End of File encountered
14                    Attempted to READ a relative record outside file boundary
21                    Invalid Key - Sequence error
22                   Invalid Key - Duplicate Key found
23                    Invalid key - No record found
24                    Invalid Key - key outside boundary of file.
30                    Permanent I/O Error
34                    Permanent I/O Error - Record outside file boundary
35                    OPEN, but file not found
37                    OPEN with wrong mode
38                    Tried to OPEN a Locked file
39                    OPEN failed, conflicting file attributes
41                   Tried to OPEN a file that is already open
42                    Tried to CLOSE a file that is not OPEN
43                    Tried to REWRITE without READing a record first
44                    Tried to REWRITE a record of a different length
46                    Tried to READ beyond End-of-file
47                   Tried to READ from a file that was not opened I-O or INPUT
48                    Tried to WRITE to a file that was not opened I-O or OUTPUT
49                    Tried to DELETE or REWRITE to a file that was not opened I-O
91                    Password or authorization failed
92                    Logic Error
93                   Resource was not available (may be allocated to CICS or another user)
94                    Sequential record unavailable or concurrent OPEN error
95                    File Information invalid or incomplete
96                    No DD statement for the file
97                    OPEN successful and file integrity verified
98                    File is Locked - OPEN failed
99                    Record Locked - record access failed.

Job Entry Subsystem - JES

noreply@blogger.com (M siva raman) — Fri, 08 Apr 2011 13:43:00 +0000

JES:

JES is an MVS subsystem that manages jobs on the mainframe. JES will receive jobs into MVS, check

the syntax, schedule jobs for processing and control job output.

Two types of JES:

1.JES2

2.JES3

1.JES2 Job processing:

There are 6 distinct phases to processing jobs with JES2 on MVS. All these phases except the

processing phase are handled by JES2, MVS handles the actual processing of a program.

1) Input Phase

During the Input Phase the JCL job stream is read from input devices such as card readers, terminals and

the Internal Reader. The Internal Reader is a special system program that is used by programs to submit

jobs, commands, and control statements to JES2 for processing.

JES2 will read the job stream and assign each job an ID, (Job Number). The job stream will then be

placed into special JES2 spool datasets ready for processing.

JES2 will select jobs from the spool datasets for processing.

2) Conversion Phase.

When a job is selected for processing, JES2 will start a converter program, which will merge any JCL

Procs into the main job stream and convert the job stream into text that JES2 and MVS can understand.

The text is stored on spool datasets.

At this stage the JCL syntax is checked for errors. If there are any errors then the job is queued for output processing (see 4. Output Processing) and no programs are run.

3) Processing Phase

In the processing phase JES2 will receive request from MVS initiators for work to process. JES2 selects a

job and sends it to be processed by MVS.

An initiator is a special MVS system program which starts a job. Jobs are assigned to an initiator based

on job classes. Initiators are assigned one or more classes, if a job has the same job class as an initiator,

then it can run on that initiator.

The initiator will build control blocks for the job and allocate the resources (files, tapes, etc) that you

specified in the JCL. The initiator will then begin executing the specified program.

4) Output Phase.

In the output phase JES2 will handle processing of the output from your job. JES2 will check the output

classes and device setup and queue the output for print or punch processing.

5) Hard Copy Phase

In this phase the output is selected for processing. The output will be sent to the printer or punch device. Once the output has been processed the job is placed on the purge (delete) queue.

6) Purge Phase

In the purge phase the space allocated on the spool datasets for your job and output is released (ie the output is deleted). Once the space is released, a message is issued to the system log to say that the output has been purged.

2.JES3:

JES3 processing is considered to be centrally controlled. One image is designated as the focal point for the entry and distribution of jobs and for the control of resources needed by the jobs. That image, called the global processor, distributes work to itself and the other images in the configuration, known as local processors. It is from the global processor that JES3 manages jobs and resources for the entire JESplex, matching jobs with available resources. JES3 manages processors
(images), I/O devices, volumes, and data. To avoid delays that result when these resources are not available, JES3 ensures that they are available before selecting the job for processing. Using this centralized approach, JES3 can make informed and complex decisions about job scheduling and placement.

Changeman Tools Tutorials

noreply@blogger.com (M siva raman) — Mon, 04 Apr 2011 05:34:00 +0000

CHANGEMAN

Changeman is version control utility of HOUSEHOLD which manages and automates the process of implementing applications/systems software from a development environment to the production environment. Changeman uses the strategy of packages which will include all the information which has to be move into the production environment. Change man does this job by managing movement of change package information in five distinct environments

1) Development The development environment is used for application program development. The development environment may or may not exists under the control of changeman

2) Staging The staging environment is a transition environment, where all the testing and editing of the work libraries are initiated

3) Baseline The baseline environment is a copy of the current production libraries which are managed by changeman. These libraries are used in the case of application testing

4) Production The production environment is a set of libraries where the production version of application resides

5) Backup The backup environment consists of the libraries which contains the previous versions of production software

A changeman package is a logical definition for the collection of items associated with a change or development request. The associated items include work data sets which are managed by changeman. In a typical change request the following can be the associated members

1) Source Code

2) Copy Books

3) Load Modules

4) DBRM libraries

5) Service request

6) JCL

When a change man package is created, it creates a set of data sets to store all the associated items or termed as COMPONENTS. The data sets are usually a Partitioned Organization ones with a unique naming convention. All the changeman controlled data sets will have a high level qualifier as OIN1. The data set will be something like

PICM.CP000000.OIN1. #NNNNNN.??? ,

where #NNNNNNN is the Changeman package number which the item or component is associated, and ??? is the associated member or component type.

Project Pneumonic:

Within the Package Master, HOUSEHOLD has divided work up by ‘Project Mnemonics’. Projects have been used to divide change management by application support groups like HLFG, OIN1 etc. There is internal security within CM that allows specifically named components to belong only to one project. For example, a payroll source member may be secured so that only payroll projects Pneumonic are authorized to access it.

There are different stages before installing the package and they are DEVelopment, PROmtion, AUDit trailing, FReeZing, APProval etc. When a package is created it will be in DEV status, once the modules/programs are checked into the package and promoted to test, the package will be in promote status. AUDit trailing will be done for that package to make sure that everything is okay. Later the package will be FRoZEn and it will be in FRZ status. Once the package gets to FRZ status nothing can be done to the programs/modules involved with it. The last stage is APProval state, i.e., the managers here have to approve our

changes and once all the approvals are obtained the package will be moved into production on the install date specified while creating the package. This is just a brief idea of how the changeman works.

WORKING WITH CHANGEMAN

The changeman utility can be accessed from the ISPF main menu by giving a C. The following screen will be displayed

--- CHANGE MAN 4.1.6P PRIMARY OPTION MENU --- NOTIFICATION UPDATED

OPTION ===>

1 Build - Create, update and review package data

2 Freeze - Freeze or unfreeze a package

3 Promote - Promote or demote a package

4 Approve - Approve or reject a package

5 List - Display (to process) package list

B Backout - Back out a package in production

C CDF - Concurrent Development Facility

D Delete - Delete or undelete a package

L Log - Browse the activity log

N Notify - Browse the Global Notification File

O OFMlist - Online Forms package list

Q Query - Query packages, components and relationships

R Revert - Revert a package to DEV status

T Tutorial - Display information about Change Man

X Exit - Exit Change Man

Press ENTER to process; enter END command to exit.

The menu itself is self explanatory regarding the options and their functions. Usually a Production move involves a change man cycles which consists of

1) Creating a Package which also involves the supplying of general information about the changes or the development activity to be performed. Packages will be created by the Module Leaders, Project Leaders or Project Managers.

2) The package contains a list of programs that we refer as ITEM or COMPONENT which has to be attached to the package. This is done either through a CHECK OUT of the ITEM or to STAGE (is discussed below in detail)

3) The programs or the item is edited or modified as per the requirements and compiled(change man generates the JCLs for compiling a component and submits the job for compilation).

4) After successfully compiling the components in your package, you may use the Promote function. This function copies components into appropriate test libraries. When promoting for the first time, you should perform a FULL PROMOTE, which takes all members in your package and promotes them to appropriate test libraries. This step is needed to test the component in your test regions. If errors are detected during testing, you can DEMOTE any or all of the members in your package. After corrections have been made, You can re-PROMOTE them to test environment.

5) When all of the components in a change package have been tested and user sign-off has been obtained, you must submit the change package for AUDIT. The audit process verifies whether or not all of your components are in synch. For example, if no changes are made to a component, the AUDIT will detect that staging and baseline libraries are duplicate.

6) After running a successful audit, the next step is to FREEZE the package. A change package must been in FRZ status before the Approval process can take place. Once a package is in the FROZEN stage you can only browse the components

7) All normal ‘planned’ application packages must be approved by PEER, MANAGER, APPLICATIONS CCB Approvers and CHANGE MANAGEMNENT Implementers.

8) Approvals must be completed prior to the Implementation date/time.

9) Once the necessary approvals have been obtained by CM, the package is ready for installation. During the installation, CM submits the migration jobs to copy all the components from staging libraries to production libraries. Once this is complete, CM sends a ‘BASELINE RIPPLE’ message to the creator of the package. This indicates all current and backup versions have been successfully updated. In the event of a back-out, CM will take the current version (0) generation and copy the -1 version into baseline

To access a particular package where you have the components to be edited or changed, note the Package number it will be usually like OIN1000060, OIN1000092

etc. Enter the option ‘5’(LIST) from the changeman menu got through ISPF main menu. The below screen is the outline when you enter on the LIST option

--------------------------- PACKAGE LIST PARAMETERS ---------------------------

COMMAND ===>

SPECIFY SELECTION CRITERIA:

PACKAGE ID ===> OIN1000092 (Full name or pattern; blank for list,

or '*' for all packages)

PACKAGE STATUS ===> (DEV, FRZ, APR, REJ, DIS, INS,

BAS, BAK, OPN, CLO, TCC or DEL)

CREATOR'S TSO-ID ===>

WORK REQUEST ID ===>

DEPARTMENT ===>

PACKAGE LEVEL ===> (1-Simple, 2-Complex,

3-Super, 4-Participating)

PACKAGE TYPE ===> (Planned or Unplanned)

PACKAGE TIME SPAN ===> (Permanent or Temporary)

FROM INSTALL DATE ===> (YYYYMMDD)

TO INSTALL DATE ===> (YYYYMMDD)

FROM CREATION DATE ===> (YYYYMMDD)

TO CREATION DATE ===> (YYYYMMDD)

OTHER PARAMETERS ===> (Y/N)

Press ENTER to process; Enter END command to exit.

The PACKAGE-ID will be the package id which was last accessed by you. If you want to accesses a package OIN1000092. Enter the package OIN1000092 in the package-id field and hit enter which will display you the package list screen which is displayed below.

COMMAND ===> SCROLL ===> CSR

PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTE AUD CREATOR

10) __ OIN1000092 DEV 20001231 SMPL PLN/PRM HIERARCHY HFC LEVEL1 VEN631

There are two types of commands which can be entered first is on the command line and second on the underscores before the package name. Here are some of the command commands which you usually enter on the package prompts

1) S1 Stage components (Dev Lib list)

2) C1 Check out components (Baseline/promotion)

3) S2 Stage components (Package list)

4) QP Query change package information

5) AP Audit a package

6) PD Promotion and Demotion

7) F1 Freezing a package online

Check out Components (Option C1)

If a component (program or copybook or subroutine, assembler table etc) is present in the baseline library which is nothing but the group of changeman Partitioned datasets (PDS). A component when checked out into a changeman package should be assigned with a type. The component type should be correct because as mentioned previously changeman generates JCLS to compile the component automatically. To tell changeman to use the correct procedure to use for compilation we should specify the type. For e.g. if we are having a simple COBOL program, then the compilation should be done only to create and a load module so changeman identifies this and uses a procedure. If there is COBOL program with DB2 access then changeman should be told to compile the program with a DB2 option i.e. generate a JCL which uses procedure for compiling a DB2 cobol program. So depending on the type the sources for the baseline library are defined to change.. As discussed previously, For each type we incorporate into a package it will go as member to a partitioned group of datasets created at the time of creating the package. The following are component types supported by changeman

LIB DESCRIPTION

_ HCA CICS Online Assembler

_ HCC CICS Online COBOL: load to CLM

_ HC2 CICS Online COBOL 2: load to CLM

_ HCD CICS Online COBOL w/DB2: load to CLM

_ HC4 CICS Online COBOL 2 w/DB2: load to CLM

_ HC5 CICS Online COBOL LE w/DB2: load to CLM

_ HC6 CICS Online COBOL LE: load to CL6

_ NDM NDM Processes (sys5.ndm.process)

_ NDJ NDM Jobs (HFCP.JOBLIB)

_ HBA Batch Assembler

_ HBC Batch COBOL: load to BLM

_ HB2 Batch COBOL 2: load to BLM

_ HBD Batch COBOL w/DB2: load to BLM

_ HB3 Batch COBOL LE

_ HB4 Batch COBOL 2 w/DB2: load to BLM

_ HB5 Batch COBOL 370 w/DB2: load to BLM

_ HCM CICS Online MAPs: load to MAP & CP1

_ DBR DBRM Library DB2 System

_ DBB DB2 Bind Control Cards for Plans & Pkgs

_ DCL DCLGEN Copybooks

_ RUN DB2 Run Cards

_ BLM Batch Load Module

_ CLM CICS Online Load Module

_ CL6 CICS Online Load Module

_ MAP Loadlib CICS MAPS

_ CT1 CICS Translator for Copybooks: load to CP1

_ CP1 Copy Books:

_ JB1 JOBs:

_ PR1 PROCs:

_ CC1 Control Cards:

_ CC2 Control Cards (HFCP.CTLCARD)

_ DMS DMS Control Cards

_ LST Compile Listing Library

_ XP1 Express: Move from test to production

_ CPY Dummy, required by Change Man. DO NOT USE

_ LOD Dummy, required by Change Man. DO NOT USE

The following are the corresponding libraries or partitioned datasets which are created for a sample package OIN1000092

LIB DEVELOPMENT STAGING LIBRARY

HB5 PICM.CP000000.OIN1.#000092.HB5

DBR PICM.CP000000.OIN1.#000092.DBR

DBB PICM.CP000000.OIN1.#000092.DBB

RUN PICM.CP000000.OIN1.#000092.RUN

BLM PICM.CP000000.OIN1.#000092.BLM

CP1 PICM.CP000000.OIN1.#000092.CP1

JB1 PICM.CP000000.OIN1.#000092.JB1

PR1 PICM.CP000000.OIN1.#000092.PR1

LST PICM.CP000000.OIN1.#000092.LST

CPY PICM.CP000000.OIN1.#000092.CPY

LOD PICM.CP000000.OIN1.#000092.LOD

The following are the baseline libraries that changeman searches when you request change man to check out any component the type and the corresponding datasets searched are also mentioned.

LIB BASELINE LIBRARY NAME

HCA PO00.CP000000.HFNP.SRX

HCC PO00.CP000000.HFNP.SRX

HC2 PO00.CP000000.HFNP.SRX

HCD PO00.CP000000.HFNP.SRX

HC4 PO00.CP000000.HFNP.SRX

HC5 PO00.CP000000.HFNP.SRX

HC6 PO00.CP000000.HFNP.SRX

NDJ HLIC.JOBLIB

NDM SYS5.NDM.PROCESS

HBA PO00.CP000000.HFNP.SRX

HBC PO00.CP000000.HFNP.SRX

HB2 PO00.CP000000.HFNP.SRX

HB3 PO00.CP000000.HFNP.SRX

HBD PO00.CP000000.HFNP.SRX

HB5 PO00.CP000000.HFNP.SRX

HB4 PO00.CP000000.HFNP.SRX

HCM PO00.CP000000.HFNP.SRX

DBR PO00.CP000000.HFNP.DBR

DBB PO00.CP000000.HFNP.BND

DCL PO00.CP000000.HFNP.DCL

RUN PO00.CP000000.HFNP.RUN

BLM PO00.CP000000.HFNP.LNK

CLM PO00.CP000000.HFNP.PGM

CL6 PO00.CP000000.HFNP.PGM

MAP PO00.CP000000.HFNP.PGM

CT1 PO00.CP000000.HFNP.SRX

CP1 PO00.CP000000.HFNP.CPY

JB1 PO00.CP000000.HFNP.JCL

PR1 PO00.CP000000.HFNP.PRC

LST PO00.CP000000.HFNP.LST

CC1 PO00.CP000000.HFNP.CTC

CC2 HFCP.CTLCARD

DMS PO00.CP000000.HFNP.DMS

XP1 SYS4.CHGMAN.DUMMY.EXPRESS

LOD SYS4.CHGMAN.DUMMY.LOD

CPY SYS4.CHGMAN.DUMMY.CPY

Coming back to the steps for checking out the component. Let us take the example of checking out a component POTEB010 which is BATCH COBOL PROGRAM WHICH USES DB2. Enter ‘C1’ at the package prompt the following screen will be displayed.

----------------------------------- CHECKOUT ----------------------------------

OPTION ===>

L - List libraries where component is located

PACKAGE ID ===> OIN1000092 (Package name)

COMPONENT NAME ===> POTEB010 (Name or Pattern for list; "ABCDEF" OR "ABC*")

Pattern of only "*" Checks Out all Components

related to Library Type.

LIBRARY TYPE ===> HB5 (Blank for list)

LANGUAGE ===> (Applies to source code; * for list)

SOURCE LIBRARY ===> 0 (Baseline 0 to -n; Promotion +1 to +n)

CHECK OUT TO ===> S (S-Staging library, P-Personal library)

PERSONAL LIBRARY ===>

LIBRARY DSORG ===> (Personal library: PDS, PDSE, SEQ, PAN, LIB)

CONFIRM REQUEST ===> YES (Y/N)

CHECKOUT MODE ===> 1 (1-Online, 2-Batch)

LOCK COMPONENT ===> NO (Y/N)

Press ENTER to process; Enter END command to exit.

. . . . . . . . . . . . . . . . . . . . . . . . . . .

1) If you don’t enter a component name, the change man will display the list of components which can be checked out. This is done by concatenating all the members in the baseline libraries mentioned above or you can enter even a pattern corresponding to the items, like you want a list of component available in the baseline with starting with PO. Enter ‘PO*’ at the component name field.

2) After selecting the component which you want to check out, the library type has to be entered, again if you don’t enter the library type, changeman prompts you on all the library types available. For our component POTEB010, the library type is HB5 because the component is COBOL370 program with DB2.

3) Language field is for specifying the language of the component which you are checking out, usually change man assumes the language according to the library type selected.

4) Confirming the request specifies the overlay of same component being checked out in any other package. If it is yes change man prompts that the component is already checked out in another package specifying the package number.

5) The batch/foreground gives you an option to check out in the batch or On line mode

Once you have done with the field entries ENTER to start the process of checking out

-------------------- CHECKOUT ---------------- LANGUAGE ASSUMED

OPTION ===>

L - List libraries where component is located

PACKAGE ID ===> OIN1000092 (Package or Application name)

COMPONENT NAME ===> POTEB010 (Blank or pattern for list;

* for all members)

LIBRARY TYPE ===> HB5 (Blank for list)

LANGUAGE ===> (Applies to source code; * for list)

SOURCE LIBRARY ===> 0 (Baseline 0 to -n; Promotion +1 to +n)

CHECK OUT TO ===> S (S-Staging library, P-Personal library)

PERSONAL LIBRARY ===>

LIBRARY DSORG ===> (Personal library: PDS, SEQ, PAN, LIB)

CONFIRM REQUEST ===> YES (Y/N)

CHECKOUT MODE ===> 1 (1-Online, 2-Batch)

Press ENTER to process; Enter END command to exit..

The message termed ‘CHECKED OUT’ or ‘LANGUAGE ASSUMED’(as in this case) may be displayed in the top right corner of the panel. Once this message comes when you are doing an online check out the same has been done by change man. If it is a batch mode then change man will prompt you about the completion of a job which confirms that the check out has been done. Note that while checking out the change man doesn’t compile the component.

Staging a component (S1)

Staging is usually done when a program is not available in the baseline libraries supported by changeman. Usual examples are when you are trying to develop a new program and put in the change man to move into production. The procedure adopted is to write the program as a member in your personal PDS and stage using the ‘S1’ option into the packages. Again let us take the example of staging an example component for better understanding, this time the component be

POTEB020 which is COBOL370 BATCH PROGRAM WHICH USES DB2, so the type is HB5. Typing ‘S1’ in the package prompt gives you a screen display below

----------------------- STAGE: FROM DEVELOPMENT ----------------- COMMAND ===>

PACKAGE ID: OIN1000092 STATUS: DEV INSTALL DATE: 20000903

ISPF LIBRARY:

PROJECT ===>

GROUP ===>

TYPE ===>

MEMBER ===> (Blank or pattern for list; * for all members)

OTHER PARTITIONED OR SEQUENTIAL DATASET:

DATASET NAME ===>

ORGANIZATION ===> (PDS, SEQ, PAN, LIB, OTH)

LIBRARY TYPE ===> (Blank for list)

LANGUAGE ===> (Blank for list; applies to source code)

STAGE NAME ===> (Optional if organization not SEQ)

CONFIRM REQUEST ===> YES (Y/N)

STAGE MODE ===> 1 (1-Foreground, 2-Batch)

SUPPRESS MESSAGES ===> (Y/N; applies to batch stage)

As described previously changeman allows you to stage from the PANVALET LIBRARY, PARTITIONED DATASETS(PERSONAL OR OTHERS),SEQUENTIAL FILE as a component to package. Specify the location of the component you want to stage in the appropriate fields and as in the check out option specify the library type and language of the component. In our example case of POTEB020 it is HB5. Now IF you are staging from the PANVALET library give the ORGANIZATION as ‘PAN’ and if you are staging from a sequential dataset then mention organization as ‘SEQ’ and mention the name in which you want to assign for the component in the package in the STAGE NAME. so after entering the request my screen will appear as

--------------------- STAGE: FROM DEVELOPMENT ------------------- COMMAND ===>

PACKAGE ID: OIN1000092 STATUS: DEV INSTALL DATE: 20000903

ISPF LIBRARY:

PROJECT ===>

GROUP ===>

TYPE ===>

MEMBER ===> (Blank or pattern for list; * for all members)

OTHER PARTITIONED OR SEQUENTIAL DATASET:

DATASET NAME ===> 'dh47.ven631.pgms(poteb020)'

ORGANIZATION ===> pds (PDS, SEQ, PAN, LIB, OTH)

LIBRARY TYPE ===> HB5 (Blank for list)

LANGUAGE ===> cobol370 (Blank for list;applies to source code)

STAGE NAME ===> (Optional if organization not SEQ)

CONFIRM REQUEST ===> YES (Y/N)

STAGE MODE ===> 1 (1-Foreground, 2-Batch)

SUPPRESS MESSAGES ===> (Y/N; applies to batch stage)

Unlike checkout staging compiles the program before staging into the package specified, so when you ‘ENTER’ to process the staging of the component in this screen it will show you the options for compilations, which is similar to compilation screens of the compile option of a component from a package. The first screen will appear as shown below.

------------------------- STAGE: COMPILE AND LINK EDIT ------------------------

COMMAND ===>

PACKAGE ID: OIN1000092 STATUS: DEV INSTALL DATE: 20001231

STAGED NAME: POTEB020

LIBRARY TYPE: HB5 - Batch COBOL 370 w/DB2: load to BLM

LANGUAGE: COBOL370

DATASET NAME: DH47.VEN631.PGMS

COMPILE PROCEDURE ===> COBOL370 (Blank for list; ? for designated procedure)

COMPILE PARMS ===>

(Enter JOB Name for PROCs requiring associated JOB for JCLCHECK)

LINK EDIT PARMS ===>

DB2 PRE-COMPILE ===> Y (Y/N)

OTHER OPTIONS ===> YES (Y to display other options)

JOB STATEMENT INFORMATION:

===> //VEN631E JOB (H54D,ITIT),'RAVI', <=== CHANGE ACCORDINGLY_____

===> // CLASS=S, <=== CHANGE ACCORDINGLY_____

===> // NOTIFY=VEN631, <=== CHANGE ACCORDINGLY_____

===> // MSGCLASS=T <=== CHANGE ACCORDINGLY_____

Press ENTER to process; Enter END command to exit.

. . . . . . . . . . . . . . . . . . . . . . . . . . .

Precaution to be taken in this screen is to verify if the Job log is mentioned in the JOB STATEMENT information, if not please key in the above information changing the user-id of VEN631 to yours. The above is initial screen displayed before submitting a job of compilation and link edit. ‘ENTER’ in the screen will show you the compilation and link-edit parameters that is required for the program.

If the program has a DB2 attachment then the next screen will ask you to select the DB2 system where the program is going to be attached. Select the DB2 system by saying a ‘S’ in the prompt of the systems as below and ‘ENTER’

---- DB2 PHYSICAL SUBSYSTEMS ---------- Row 1 to 4 of 4

COMMAND ===> SCROLL ===> CSR

VERSION ===> ________________________________________________________

Enter S to select a DB2 subsystem and continue.

Enter END command to exit.

DB2 REMOTE DB2 SYSTEM

SUBSYS SITE LOAD LIBRARY

_ DB2T SYS4.DB2.DB2D.SDSNLOAD

_ DSNP SYS4.DB2.DSNP.SDSNLOAD

S DB2D SYS4.DB2.DB2D.SDSNLOAD

_ DBLP DB2PHFC.DSNLOAD

******************************* Bottom of data ********************************

The next screen shows the parameters of the COMPILATION AND LINK EDIT

----------------------------- STAGE: USER OPTIONS -----------------------------

COMMAND ===>

NAME: POTEB999 TYPE: HB5 LANGUAGE: COBOL370

COMPILE ONLY ===> ??? IMS DLITCBL ENTRY ===>

CICS PRE-COMPILE ===> DROP INCLUDE STMTS ===>

EASYTRIEVE NO NAME ===> XPEDITER COMPILE ===>

FORMAT TO IMSTEST ===> INCLUDE MQSERIES ===>

(TEST MFS IS DEFAULT)

JCK FULL LISTING ===> USER OPTION 10 ===>

USER OPTION 11 ===> USER OPTION 12 ===>

USER OPTION 13 ===> USER OPTION 14 ===>

USER OPTION 15 ===> USER OPTION 16 ===>

USER OPTION 17 ===> USER OPTION 18 ===>

USER OPTION 19 ===> USER OPTION 20 ===>

Use Y or N to select or deselect additional processing options;

Press ENTER to continue; Enter END command to exit.

. . . . . . . . . . . . . . . . . . . . . . . . . . .

The first two fields are generally blank.

XPEDITER This field specifies whether the program has to be compiled with the debug XPEDITE option or not

Hitting ‘Enter’ in this screen will submit a job for compilation. Note down the job name and Job number for the reference for any compilation and link edit mistakes.

The extra step you should do in the checkout is to edit and recompile so that it will be in ready for testing.

PACKAGE LIST(S2)

Package list is to view the components attached with the package. To view the package list on the package prompt enter the ‘S2’ as displayed below

----------------------------- CHANGE PACKAGE LIST ------------ Row 1 to 1 of 1

COMMAND ===> SCROLL ===> CSR

PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTE AUD CREATOR

S2 OIN1000187 DEV 20001231 SMPL PLN/PRM HTS VEN631

******************************* Bottom of data ********************************

You will be getting a screen as displayed below showing the list of members.

------------------------- STAGE: OIN1000023 COMPONENTS ------- Row 1 to 3 of 3

COMMAND ===> SCROLL ===> CSR

NAME TYPE STATUS CHANGED LANGUAGE PROCNAME ID REQUEST

__ BUSUNIT DBB ACTIVE 20001030 080517 VEN631

__ BUSUNIT HB5 ACTIVE 20001102 083720 COBOL370 COBOL370 VEN631

__ POTEB020 HB5 ACTIVE 20001101 125342 COBOL2 COBOL370 VEN631

******************************* Bottom of data ********************************

The Members of the package is displayed in the alphabetic order, The various columns specifies characteristic of the Components.

Name : Specifies the name of the component

Type : Specifies the library type of the component

Status :Specifies the current status of the component saying where it is compiled(ACTIVE), edited but not compiled (INCOMP),Frozen (FROZEN),Checked out(Check out).

Changed : Specifies the date and time when the component was last modified

Language: Language of the Component

Procname: Procedure used to compile the component when submitting a job for compilation

ID : Indicates the ID of the person who has last compiled, edited or

promoted the component.

Request : Message field which prints the request who have made to the

component if you are doing some kind of editing, browsing etc.

Editing, Browse and recompiling a Component

After doing a list on the components you may have to edit, browse or recompile the component according to the need. For editing the component first position the cursor on the component’s prompt on the screen mentioned and Enter a ‘E’ , the screen opens the component for editing, after editing if you want to save the changes you have to go through a compilation cycle (mentioned above) other wise all the changes will be lost. Change man automatically indicates the screens for recompilation (mentioned above) plus two screens ahead of compilation screens showing the changes made. Do the full cycle of compilation, even though you are sure that there will be compilation errors.

Let us take for example you are going to edit the component POTEB020 in the above package. Put an ‘E’ in from of the component as displayed below and hit ‘Enter’

------------------------- STAGE: OIN1000023 COMPONENTS ------- Row 1 to 3 of 3

COMMAND ===> SCROLL ===> CSR

NAME TYPE STATUS CHANGED LANGUAGE PROCNAME ID REQUEST

_ BUSUNIT DBB ACTIVE 20001030 080517 VEN631

__ BUSUNIT HB5 ACTIVE 20001102 083720 COBOL370 COBOL370 VEN631

E POTEB020 HB5 ACTIVE 20001101 125342 COBOL2 COBOL370 VEN631

******************************* Bottom of data ********************************

You will get the edit screen for the POTEB020 program showing the source code. Let us say you have edited the programs name to ‘XXXX’, When you end the editing process the next screen displayed will show you where the changes were made like below.

The differences are mentioned with a ‘D’ and ‘I’ indicating Deleted and Inserted lines in the old existing component and the changed component respectively. Press the function key ‘F3’ to quit from this screen

Menu Utilities Compilers Help

BROWSE D131.VEN631.CMN00307.T1604049.OUTLIST Line 00000000 Col 001 080

Command ===> Scroll ===> CSR

********************************* Top of Data **********************************

S E R C M P A R (MVS-3.1.1 - 1997/213) CHSERV THURSDAY NOVE

SYSUT1=PICM.CP000000.OIN1.#000175.HB2(CELETRS),SYSUT2=D131.VEN631.CMN00307.T1604

000100 IDENTIFICATION DIVISION.

000200 PROGRAM-ID. POTEB020.

++++++++|+++.+<++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7+>

D 000300 AUTHOR. Ravi K Gummadapu.

--------|---.----1----.----2----.----3----.----4----.----5----.----6----.----7--

I 000300 AUTHOR. Ravi K Gummadapu..

++++++++|+++.+<++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7+>

000400******************************************************************

000500* 08/15/99 SR00084 - CUSTOMER SERVICE LETTER PROJECT

000600* EXTRACT CUSTOMER RECORDS FOR THOSE WHO HAVE INSURANCE ON

000700* THEIR LOANS. LETTERS WILL BE GENERATED BASED ON THE FILE

000800* CREATED IN THIS PROGRAM.

SER71I - END OF TEXT ON FILE SYSUT1

SER72I - END OF TEXT ON FILE SYSUT2

SER75I - RECORDS PROCESSED: SYSUT1(257)/SYSUT2(257),DIFFERENCES(1)

. . . . . . . . . . . . . . . . . . . . . . . . . . .

Pressing the function key ‘F3’ gives you the below screen which queries you to keep the outlist dataset,to print it or to delete. Usually the option is to delete ‘D’ the outlist dataset showing the difference.

------------------------ COMPARISON REPORT DISPOSITION ------------------------

OPTION ===>

REPORT DATASET NAME: 'D131.VEN631.CMN00307.T1604049.OUTLIST'

REPORT DISPOSITION ===> D D - Delete

K - Keep

PD - Print and Delete

PK - Print and Keep

JOB STATEMENT INFORMATION IF DISPOSITION IS PD OR PK:

===> //VEN631E JOB (H54D,ITIT),'RAVI', <=== CHANGE ACCORDINGLY_____

===> // CLASS=S, <=== CHANGE ACCORDINGLY_____

===> // NOTIFY=VEN631, <=== CHANGE ACCORDINGLY_____

===> // MSGCLASS=T <=== CHANGE ACCORDINGLY_____

Press ENTER or END to process

Enter CANCEL command to exit without saving changes.

. . . . . . . . . . . . . . . . . . . . . . . . . . .

Then what follows will be compilation and Link-edit screen discussed previously.

To browse a Component Just put ‘B’ in the prompt of the component and enter it will display you the component contents.

To recompile the component put a ‘R’ in the prompt of the component and Enter to get the same compile screens mentioned above. This is usually done when you want to recompile without editing the component. A component can be recompiled only when the status of the component is in the ‘ACTIVE’ or ‘INCOMP’ stage.

Note: When a package is FROZEN or when the install date has elapsed then the component in the package are unusable until the status is changed or install date is modified.

What does Compilation do to the component?

When a component is edit or recompiled, the status of the component becomes INCOMP. If the Compilation is successfully, the status changes back to ACTIVE. This can be seen only be refreshing the PACKAGE LIST., i.e. by saying ‘F3’ in the package list and entering the package list command ‘S2’ again. Compilation and link-edit creates a load module in the package PDS i.e. it creates a load module and stores it in the load library created by the package at the time of package’s creation.

PROMOTION AND DEMOTION(PD)

For testing purpose, it is needed that all the load modules created should be present in the test load libraries, and in case of the DB2 programs a plan has to be created in addition to the load-module. All this functionality are done when you are PROMOTING a component. DEMOTING reverses the previous promotion activity and restores the previously existing load libraries. When you are promoting the components in the package, you have the option for promoting all the components or promoting just one component or a list of components at a time. But ensure that before doing the Promotion the component is compiled successfully without any errors. For PROMOTING ENTER A ‘PD’ in the package list screen after ending the ‘S2’ option i.e. on the screen which looks like the below displayed one

NOTE: First time Promoting a package should be FULL PROMOTION.

----------------------------- CHANGE PACKAGE LIST ------------ Row 1 to 1 of 1

COMMAND ===> SCROLL ===> CSR

PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTE AUD CREATOR

PD OIN1000023 DEV 20001231 SMPL PLN/PRM HTS VEN631

******************************* Bottom of data ********************************

It will prompt you with a panel display below which allows to specify the options of Promotion, Demotion or Overlay(whether you are going to overlay some other’s load module or not). The columns under the entry fields mentions the history of the promotion and demotion activity done on this package by different persons. After ‘Entering’ the desired option in the action field say ‘P’ you will get a screen like the below displayed one.

The next panel may be a PROMOTION/DEMOTION PANEL, the one displayed below is a promotion panel. The example we are going to take is to promote a component POTEB020 of the above-mentioned package.

---------------------------- PROMOTE CHANGE PACKAGE -------- Row 1 to 10 of 17

COMMAND ===> SCROLL ===> CSR

PACKAGE ID: OIN1000092 CREATOR: VEN631 STATUS: DEV INSTALL DATE: 20001231

CURRENT PROMOTION LEVEL: LEVEL1 - 1

MAXIMUM PROMOTION LEVEL: LEVEL3 - 3

ACTION REQUESTED ===> p (P-Promote, D-Demote, C-Check for overlay)

ONLINE OR BATCH ===> B (O-Online, B-Batch)

LEVEL TO CHECK ===> 1 (Required for Action C)

PROMOTE/DEMOTE HISTORY LVL NICKNAME DATE TIME ID

Full Promotion 1 LEVEL1 2000/11/02 08:38 VEN631

Full Demotion 1 LEVEL1 2000/11/02 08:37 VEN631

Full Promotion 1 LEVEL1 2000/11/01 12:58 VEN631

Full Demotion 1 LEVEL1 2000/11/01 12:56 VEN631

. . . . . . . . . . . . . . . . . . . . . . . . . . .

In the option field of the above screen, Choose ‘F’ to do a full promotion or demotion (which depends on the option you have chose on the previous panel) which means that all the components of the package will be promoted, but an ‘S’ in the option field will let you select the components you want to promote or demote. In the NEXT PROMOTION LEVEL field mention the promotion level, generally ‘1’ is used by us to do the testing. ‘2’ will copy the already compiled load modules from the package load libraries to a user acceptance load library, other than test. The selective promotion will prompt you a screen like below. We are considering the example of promoting a component POTEB020 in the above-mentioned package.

------------------------------- PROMOTE OPTIONS -------------------------------

OPTION ===> s

F - Full promotion of the entire package to another promotion level

S - Selective promotion of components to another promotion level

PACKAGE ID: OIN1000092 CREATOR: VEN631 STATUS: DEV INSTALL DATE: 20001231

CURRENT PROMOTION LEVEL: LEVEL1 - 1

MAXIMUM PROMOTION LEVEL: LEVEL3 - 3

NEXT PROMOTION LEVEL ===> 1

BYPASS OVERLAY CHECK ===> NO (Y-Yes or N-No)

JOB STATEMENT INFORMATION:

===> //VEN631E JOB (H54D,ITIT),'RAVI', <=== CHANGE ACCORDINGLY_____

===> // CLASS=S, <=== CHANGE ACCORDINGLY_____

===> // NOTIFY=VEN631, <=== CHANGE ACCORDINGLY_____

===> // MSGCLASS=T <=== CHANGE ACCORDINGLY_____

Press ENTER to process; Enter END command to exit.

. . . . . . . . . . . . . . . . . . . . . . . . . . .

---------------------- PROMOTE: OIN1000092 COMPONENTS ------ Row 1 to 4 of 4

COMMAND ===> SCROLL ===> CSR

Enter END command to process or CANCEL to exit.

CURRENT PACKAGE PROMOTION LEVEL: 1 - LEVEL1

NEXT COMPONENT PROMOTION LEVEL: 1 - LEVEL1

NAME TYPE ALIAS-OF PROMOTION DATE TIME ID STATUS

_ BUSUNIT BLM 0 STAGING 2000/11/02 08:37 VEN631

_ BUSUNIT DBB 0 STAGING 2000/10/30 08:05 VEN631

S POTEB020 BLM 0 STAGING 2000/11/02 16:08 VEN631

******************************* Bottom of data ********************************

. . . . . . . . . . . . . . . . . . . . . . . . . . .

When you are promoting a component put an ‘S’ on all the type of same component you want to promote or demote this will avoid any procedural error of preparing or backing out a component. You can select only the items which are marked as ‘STAGING’ in the promotion column of the above panel.. In this panel after selecting the component related type ‘Enter’ and ‘End’ the screen to submit a promotion or demotion job accordingly. When the Promotion job ends successfully, the components will be available in the TEST LOAD LIBRARIES or USER ACCEPTANCE LOAD LIBRARIES for testing purposes.

Once a component is promoted, if the component happens to be a CICS program then you may have to do a NEWC in the respective test region to test for the changes you have made to the component.

QUERY PACKAGE (QP)

The query package in the package selection list will give you a panel with a lot of lines with a prompt at the beginning, each of the row items are self-explanatory. All the rows gives information and component details regarding the package you are querying on.

OVERLAY WARNING

Suppose user VEN631 working with a program POTEB020 which is checked out in the package OIN1000092. You are trying to checkout the same program in a different package OIN1000183 then you will see the following screen.

---------------------------------- POTEB020.HB5 --------------- Row 1 to 1 of 1

COMMAND ===> SCROLL ===> CSR

Press ENTER or END to process or enter CANCEL command to exit.

This component is included in the following packages:

PACKAGE ID STA PROMOTION VV.MM LAST ACTION SIZE PROCNAME ID

OIN1000092 DEV 05.03 2000/11/02 08:37 157 COBOL370 VEN631

******************************* Bottom of data ********************************

Enter CANCEL here so that the program doesn’t get checked out in the package OIN1000183 and notify the Onsite coordinator with the program name.

IMPORTANT NOTES:

C H A N G E M A N I N F O

PACKAGE PROMOTION:

LEVEL 1 - HITRGI2/CICSD0U0

LEVEL 2 - HITRGP2/CICSQ0U0

LEVEL 3 - HITRGJ2/CICSD0U1

TO MOVE A CHANGE FROM ONE REGION TO ANOTHER IT IS NECESSARY TO DEMOTE THE PROGRAM AND THEN PROMOTE TO THE NEW LEVEL.

(IE. D0U0 TO Q0U0 - DEMOTE FROM LEVEL 1 THEN PROMOTE TO LEVEL 2)

AT THIS TIME DB2 WILL BE SHARED ACROSS THE LEVELS SO IN THIS CASE YOU

CANNOT TEST THE SAME PROGRAM IN MULTIPLE REGIONS BECAUSE WHEN THE OTHER PERSON PROMOTES(BINDS) THEIR PROGRAM THE FIRST PROMOTE(BIND) WILL NO LONGER BE IN EFFECT

NON-DB2 PROGRAMS CAN BE TESTED IN MULTIPLE REGIONS CONCURRENTLY

BECAUSE THE LOAD LIBRARIES ARE UNIQUE FOR EACH REGION

-------------------------------------------- THE END ----------------------------------------------------------

Mainframe Reacent Placement Interview Questions and Answers

noreply@blogger.com (M siva raman) — Sat, 26 Mar 2011 14:22:00 +0000

Hi Friends this Vijai, I recently attend a Mainframe interview in Chennai. I share some Mainframe interview questions With you, What I remember …….

COBOL Questions:

1. Program name: P1.
Load library: TRGF99.COBOL.LOADLIB
Input File: TRGF99.FILE1
Output File: TRGF99.OUTFILE

//JOB1 JOB 124
//STEP01 EXEC PGM=P1
//STEPLIB DD DSN=TRGF99.COBOL.LOADLIB1,DISP=SHR
//INFILE DD DSN=TRGF99.FILE1,DISP=SHR
//OUTFILE DD DSN=TRGF99.OUTFILE,DISP=MOD

In the above scenario, if we execute the above program which one of the following errors we get?

a) S806 b)SE37 c)S0C4 d)S0C7
-------------------------------------------------------------------------------------------

2. If ‘MAINPGM’ is a COBOL program that calls another program ‘LINKPGM’ and passes a value say, ‘10’, that value will be accepted by another variable in link program. Where that variable is declared?

a) Working Storage Section of MAINPGM
b) Linkage Section of MAINPGM
c) Linkage Section of LINKPGM
d) Working Storage Section of LINKPGM
e) Both b & d
---------------------------------------------------------------------------------------

3. A file attribute mismatch was encountered. Which of the following status code is related to the above message?
a)35 b)39 c)46 d)90
---------------------------------------------------------------------------------------

4. Which of the following divisions are mandatory
i) IDENTIFICATION
ii) ENVIRONMENT
iii) DATA
iv) PROCEDURE

a) i only b) i & ii c) iv only d) i & iv e) iii & iv
-------------------------------------------------------------------------------------------

5. 01 WS-ABC PIC X.
88 FOUND VALUE ‘Y’.
88 NOT-FOUND VALUE ‘N’.
What is the error in the above code?

a) PIC clause is missing in the FOUND declaration.
b) PIC clause is missing in the NOT-FOUND declaration.
c) 88 level variables are declared in Area-A.
d) 01 level variable is declared in Area-A.
-------------------------------------------------------------------------------
6. Every file entry in the File Control should have a description in the File Section.
a) True b) False
-----------------------------------------------------------------------------------
7. IF A>B
IF A>C
DISPLAY ‘A’
NEXT SENTENCE
END-IF
DISPLAY ‘C’
END-IF.
DISPLAY ‘B’.

If A=10, B=5, C=7. What is the output?

a) A C B b) A B c) B d) C B
------------------------------------------------------------------------------------------
8. What is the statement that is used to stop the execution of the program?

a) GOBACK b) EXIT c) STOP RUN d) EXIT
--------------------------------------------------------------------------------------------
9. MAIN-PARA
DISPLAY ‘IN MAIN-PARA’.
PERFORM PARA1 THRU PARA2.
STOP RUN.

PARA1.
DISPLAY ‘IN PARA1’.

PARA3.
DISPLAY ‘IN PARA3’.

PARA2.
DISPLAY ‘IN PARA2’.

Assume that the above code is in the PROCEDURE DIVISION of a COBOL program. If the above program is executed, what is the output?

a) IN MAIN-PARA b) IN MAIN-PARA c) IN MAIN-PARA
IN PARA1 IN PARA1 IN PARA1
IN PARA2 IN PARA3 IN PARA2
IN PARA2 IN PARA3

d) Compilation Error as Para-names are not declared in a proper order.

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

10. Can we move a variable containing Alphanumeric value to a variable containing Numeric value?

a) Yes b) No
-----------------------------------------------------------------------------------
11. How many bytes are required to store data internally for a variable defined as PIC 9(7)V99 USAGE COMP-3.

a) 4 b) 5 c) 6 d) 9
---------------------------------------------------------------------------------
12. Find the number of bytes which will be stored in the variable EMP-RECORD
01 EMP-RECORD.
02 EMP-DATA1.
03 EMP-NAME PIC X(10).
03 EMP-SAL PIC 9(04).
02 EMP-DATA2 REDEFINES EMP-DATA1.
03 EMP-N1 PIC X(12).
03 EMP-N2 PIC 9(02).
02 EMP-DATA3.
03 DEPT1 PIC X(02).
03 DEPT2 PIC X(02).

a) 14 b) 16 c) 18 d) 32
-------------------------------------------------------------------------------------

13. A PIC 9(2)V9(3) VALUE 10.121
B PIC 9(2) VALUE 12
C PIC 9(2)V99 VALUE 11.23

What will be the value in C after the following statement is executed
ADD A, B GIVING C ROUNDED

a) 22.121 b) 22.12 c) 22.13 d) 11.23

Changeman Life Cycle

noreply@blogger.com (M siva raman) — Mon, 24 Jan 2011 12:22:00 +0000

Changeman life Cycle-View More Information

DELETE A RECORD IN RRDS CLUSTER

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 05:02:00 +0000

***** DELETE A RECORD IN RRDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. DELR.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS RELATIVE

RELATIVE KEY IS REL-KEY

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

05 ENO PIC 9(4).

05 ENAME PIC X(4).

05 SAL PIC 9(5).

05 FILLER PIC X(67).

WORKING-STORAGE SECTION.

01 FS1 PIC 9(2).

01 REL-KEY PIC 9(4).

PROCEDURE DIVISION.

OPEN I-O IN-FILE.

DISPLAY "FS1: " FS1.

MOVE 2 TO REL-KEY.

DELETE IN-FILE

DISPLAY "FS1: " FS1.

CLOSE IN-FILE.

STOP RUN.

***** DELETE A RECORD IN KSDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. DELR.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS INDEXED

RECORD KEY IS ENO

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

05 ENO PIC 9(4).

05 ENAME PIC X(4).

05 SAL PIC 9(5).

05 FILLER PIC X(67).

WORKING-STORAGE SECTION.

01 FS1 PIC 9(2).

PROCEDURE DIVISION.

OPEN I-O IN-FILE.

DISPLAY "FS1: " FS1.

MOVE 0002 TO ENO.

DELETE IN-FILE

DISPLAY "FS1: " FS1.

CLOSE IN-FILE.

STOP RUN.

File Program's in COBOL:

REWRITE A RECORD IN KSDS CLUSTER

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 05:01:00 +0000

***** REWRITE A RECORD IN KSDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. DELR.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS INDEXED

ACCESS MODE IS RANDOM

RECORD KEY IS ENO

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

05 ENO PIC 9(4).

05 ENAME PIC X(4).

05 SAL PIC 9(5).

05 FILLER PIC X(67).

WORKING-STORAGE SECTION.

01 FS1 PIC 9(2).

PROCEDURE DIVISION.

OPEN I-O IN-FILE.

DISPLAY "FS1: " FS1.

MOVE 0003 TO ENO.

MOVE "HHHH" TO ENAME.

MOVE 70000 TO SAL.

DISPLAY "FS1: " FS1.

REWRITE IN-REC INVALID KEY DISPLAY "NOT DONE".

CLOSE IN-FILE.

STOP RUN.

File Program's in COBOL:

REWRITE A RECORD IN RRDS CLUSTER

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 05:00:00 +0000

***** REWRITE A RECORD IN RRDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. DELR.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS RELATIVE

RELATIVE KEY IS REL-KEY

ACCESS MODE IS RANDOM

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

05 ENO PIC 9(4).

05 ENAME PIC X(4).

05 SAL PIC 9(5).

05 FILLER PIC X(67).

WORKING-STORAGE SECTION.

01 REL-KEY PIC 9.

01 OUTREC.

02 ENO1 PIC 9(4).

02 ENAME1 PIC X(4).

02 SAL1 PIC 9(5).

01 FS1 PIC 9(2).

PROCEDURE DIVISION.

OPEN I-O IN-FILE.

DISPLAY "FS1: " FS1.

MOVE 9 TO REL-KEY.

MOVE 0005 TO ENO1.

MOVE "HHHH" TO ENAME1.

MOVE 70000 TO SAL1.

MOVE OUTREC TO IN-REC.

DISPLAY "FS1: " FS1.

REWRITE IN-REC INVALID KEY DISPLAY "NOT DONE".

CLOSE IN-FILE.

STOP RUN.

File Program's in COBOL:

INSERT A RECORD IN KSDS CLUSTER

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:59:00 +0000

***** INSERT A RECORD IN KSDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. DELR.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS INDEXED

ACCESS MODE IS RANDOM

RECORD KEY IS ENO

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

05 ENO PIC 9(4).

05 ENAME PIC X(4).

05 SAL PIC 9(5).

05 FILLER PIC X(67).

WORKING-STORAGE SECTION.

01 FS1 PIC 9(2).

PROCEDURE DIVISION.

OPEN I-O IN-FILE.

DISPLAY "FS1: " FS1.

MOVE 0002 TO ENO.

MOVE "TTTT" TO ENAME.

MOVE 70000 TO SAL.

DISPLAY "FS1: " FS1.

WRITE IN-REC.

CLOSE IN-FILE.

STOP RUN.

File Program's in COBOL:

INSERT A RECORD IN RRDS CLUSTER

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:58:00 +0000

***** INSERT A RECORD IN RRDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. DELR.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS RELATIVE

ACCESS MODE IS RANDOM

RELATIVE KEY IS REL-KEY

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

05 ENO PIC 9(4).

05 ENAME PIC X(4).

05 SAL PIC 9(5).

05 FILLER PIC X(67).

WORKING-STORAGE SECTION.

01 REL-KEY PIC 9.

01 OUTREC.

02 ENO1 PIC 9(4).

02 ENAME1 PIC X(4).

02 SAL1 PIC 9(5).

01 FS1 PIC 9(2).

PROCEDURE DIVISION.

OPEN I-O IN-FILE.

DISPLAY "FS1: " FS1.

MOVE 2 TO REL-KEY.

MOVE 0002 TO ENO1.

MOVE "TTTT" TO ENAME1.

MOVE 70000 TO SAL1.

MOVE OUTREC TO IN-REC.

DISPLAY "FS1: " FS1.

WRITE IN-REC.

CLOSE IN-FILE.

STOP RUN.

File Program's in COBOL:

FETCH RECORDS BY USIING DYNAMIC IN KSDS CLUSTER

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:57:00 +0000

***** FETCH RECORDS BY USIING DYNAMIC IN KSDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. SEARCHS.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS INDEXED

ACCESS MODE IS DYNAMIC

RECORD KEY IS ENO

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

02 ENO PIC 9(4).

02 ENAME PIC X(4).

02 SAL PIC 9(5).

02 FILLER PIC X(67).

WORKING-STORAGE SECTION.

77 FS1 PIC 9(2).

77 REL-KEY PIC 9.

01 IN-REC1.

03 ENO1 PIC 9(4).

03 ENAME1 PIC X(4).

03 SAL1 PIC 9(5).

03 FILLER PIC X(67).

PROCEDURE DIVISION.

PERFORM OPEN-PARA.

MOVE 0003 TO ENO

START IN-FILE

KEY IS = ENO

INVALID KEY GO TO CLOSE-PARA.

PERFORM SEARCH-PARA.

OPEN-PARA.

OPEN I-O IN-FILE.

SEARCH-PARA.

READ IN-FILE NEXT RECORD INTO IN-REC1

AT END DISPLAY "END".

IF ENO = ENO1

MOVE IN-REC TO IN-REC1

DISPLAY IN-REC1

ELSE

DISPLAY "NOT FOUND"

GO TO SEARCH-PARA.

CLOSE-PARA.

CLOSE IN-FILE.

STOP RUN.

File Program's in COBOL:

FETCHING RECORDS BY USING DYNAMIC IN RRDS CLUSTER

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:56:00 +0000

***** FETCHING RECORDS BY USING DYNAMIC IN RRDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. SEARCHS.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS RELATIVE

ACCESS MODE IS DYNAMIC

RELATIVE KEY IS ENO1

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

02 ENO PIC 9(4).

02 ENAME PIC X(4).

02 SAL PIC 9(5).

02 FILLER PIC X(67).

WORKING-STORAGE SECTION.

77 FS1 PIC 9(2).

77 REL-KEY PIC 9.

01 IN-REC1.

03 ENO1 PIC 9(4).

03 ENAME1 PIC X(4).

03 SAL1 PIC 9(5).

03 FILLER PIC X(67).

PROCEDURE DIVISION.

PERFORM OPEN-PARA.

MOVE 3 TO ENO1

START IN-FILE

KEY IS = ENO1

INVALID KEY GO TO CLOSE-PARA.

PERFORM SEARCH-PARA.

OPEN-PARA.

OPEN I-O IN-FILE.

SEARCH-PARA.

READ IN-FILE NEXT RECORD INTO IN-REC1

AT END DISPLAY "END".

IF ENO1 = ENO

MOVE IN-REC TO IN-REC1

DISPLAY IN-REC1

ELSE

DISPLAY "NOT FOUND"

GO TO SEARCH-PARA.

CLOSE-PARA.

CLOSE IN-FILE.

STOP RUN.

File Program's in COBOL:

FETCH A RECORD BY USING RANDOM IN KSDS CLUSTER

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:55:00 +0000

***** FETCH A RECORD BY USING RANDOM IN KSDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. SEARCHR.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS INDEXED

ACCESS MODE IS RANDOM

RECORD KEY IS ENO

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

02 ENO PIC 9(4).

02 ENAME PIC X(4).

02 SAL PIC 9(5).

02 FILLER PIC X(67).

WORKING-STORAGE SECTION.

77 FS1 PIC 9(2).

77 REL-KEY PIC 9(4).

01 IN-REC1.

03 ENO1 PIC 9(4).

03 ENAME1 PIC X(4).

03 SAL1 PIC 9(5).

03 FILLER PIC X(67).

PROCEDURE DIVISION.

PERFORM OPEN-PARA.

PERFORM SEARCH-PARA.

PERFORM CLOSE-PARA.

OPEN-PARA.

OPEN INPUT IN-FILE.

MOVE 0003 TO ENO.

SEARCH-PARA.

READ IN-FILE RECORD INTO IN-REC1

IF ENO = ENO1

MOVE ENO1 TO ENO

MOVE ENAME TO ENAME1

MOVE SAL TO SAL1

DISPLAY IN-REC1

ELSE

COMPUTE ENO = ENO + 1

GO TO SEARCH-PARA.

CLOSE-PARA.

CLOSE IN-FILE.

STOP RUN.

File Program's in COBOL:

FETCH A RECORD BY USING RANDOM IN RRDS CLUSTER

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:54:00 +0000

***** FETCH A RECORD BY USING RANDOM IN RRDS CLUSTER *****

IDENTIFICATION DIVISION.

PROGRAM-ID. SEARCHS.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT IN-FILE ASSIGN TO DD1

ORGANIZATION IS RELATIVE

ACCESS MODE IS RANDOM

RELATIVE KEY IS ENO1

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD IN-FILE.

01 IN-REC.

02 ENO PIC 9(4).

02 ENAME PIC X(4).

02 SAL PIC 9(5).

02 FILLER PIC X(67).

WORKING-STORAGE SECTION.

77 FS1 PIC 9(2).

01 ENO2 PIC 9(4).

77 EOF PIC X.

77 REL-NO PIC 9.

01 IN-REC1.

03 ENO1 PIC 9(4).

03 ENAME1 PIC X(4).

03 SAL1 PIC 9(5).

03 FILLER PIC X(67).

PROCEDURE DIVISION.

PERFORM OPEN-PARA.

PERFORM SEARCH-PARA.

PERFORM CLOSE-PARA.

OPEN-PARA.

OPEN INPUT IN-FILE.

MOVE 4 TO ENO1.

SEARCH-PARA.

READ IN-FILE RECORD INTO IN-REC1

IF ENO1 = ENO

MOVE ENO TO ENO1

MOVE ENAME TO ENAME1

MOVE SAL TO SAL1

DISPLAY IN-REC1

ELSE

COMPUTE ENO1 = ENO1 + 1

GO TO SEARCH-PARA.

CLOSE-PARA.

CLOSE IN-FILE.

STOP RUN.

File Program's in COBOL:

RUNJCL TO KSDS CLUSTER(WRITE)

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:53:00 +0000

***** RUNJCL TO KSDS CLUSTER(WRITE) *****

IDENTIFICATION DIVISION.

PROGRAM-ID. MEM3.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT OUT-FILE ASSIGN TO DD1

ORGANIZATION IS INDEXED

RECORD KEY IS ENO

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD OUT-FILE.

01 OUT-REC.

02 ENO PIC 9(4).

02 ENAME PIC X(4).

02 SAL PIC 9(5).

02 FILLER PIC X(67).

WORKING-STORAGE SECTION.

01 IN-FILE.

02 OUTDATA OCCURS 3 TIMES.

03 ENO1 PIC 9(4).

03 ENAME1 PIC X(4).

03 SAL1 PIC 9(5).

77 FS1 PIC 9(2).

77 I PIC 9.

PROCEDURE DIVISION.

PERFORM OPEN-PARA.

PERFORM ACCEPT-PARA 3 TIMES.

PERFORM CLOSE-PARA.

OPEN-PARA.

OPEN OUTPUT OUT-FILE.

ACCEPT-PARA.

MOVE 1 TO I.

ACCEPT ENO1(I).

ACCEPT ENAME1(I).

ACCEPT SAL1(I).

WRITE OUT-REC FROM IN-FILE.

COMPUTE I = I + 1.

CLOSE-PARA.

CLOSE OUT-FILE.

STOP RUN.

File Program's in COBOL:

RUNJCL TO RRDS (WRITE)

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:52:00 +0000

***** RUNJCL TO RRDS (WRITE) *****

IDENTIFICATION DIVISION.

PROGRAM-ID. MEM3.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT OUT-FILE ASSIGN TO DD1

ORGANIZATION IS RELATIVE

RELATIVE KEY IS ENO2

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD OUT-FILE.

01 OUT-REC.

02 ENO PIC 9(4).

02 ENAME PIC X(4).

02 SAL PIC 9(5).

02 FILLER PIC X(67).

WORKING-STORAGE SECTION.

01 ENO2 PIC 9.

01 IN-FILE.

02 OUTDATA OCCURS 3 TIMES.

03 ENO1 PIC 9(4).

03 ENAME1 PIC X(4).

03 SAL1 PIC 9(5).

77 FS1 PIC 9(2).

77 I PIC 9.

PROCEDURE DIVISION.

PERFORM OPEN-PARA.

PERFORM ACCEPT-PARA 3 TIMES.

PERFORM CLOSE-PARA.

OPEN-PARA.

OPEN OUTPUT OUT-FILE.

ACCEPT-PARA.

MOVE 1 TO I.

ACCEPT ENO1(I).

ACCEPT ENAME1(I).

ACCEPT SAL1(I).

WRITE OUT-REC FROM IN-FILE.

COMPUTE I = I + 1.

CLOSE-PARA.

CLOSE OUT-FILE.

STOP RUN.

File Program's in COBOL:

PS TO KSDS CLUSTER (WRITE)

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:51:00 +0000

***** PS TO KSDS CLUSTER (WRITE) *****

IDENTIFICATION DIVISION.

PROGRAM-ID. MEM3.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT PSFILE ASSIGN TO DD1.

SELECT KSDSFILE ASSIGN TO DD2

ORGANIZATION IS INDEXED

RECORD KEY IS KS-EC

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD PSFILE.

01 PSREC.

02 PS-EC PIC 9(4).

02 PS-EN PIC X(4).

02 FILLER PIC X(72).

FD KSDSFILE.

01 KSDSREC.

02 KS-EC PIC 9(4).

02 KS-EN PIC X(4).

02 FILLER PIC X(72).

WORKING-STORAGE SECTION.

77 FS1 PIC X(2).

PROCEDURE DIVISION.

OPEN INPUT PSFILE.

OPEN OUTPUT KSDSFILE.

PERFORM READ-PARA.

READ-PARA.

READ PSFILE AT END CLOSE PSFILE, KSDSFILE

STOP RUN.

MOVE PSREC TO KSDSREC.

WRITE KSDSREC.

DISPLAY KSDSREC.

GO TO READ-PARA.

File Program's in COBOL:

PS to RRDS Cluster -Writing Records

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:48:00 +0000

VSAM FILES WITH COBOL PROGRAMS

***** PS TO RRDS CLUSTER (WRITING) *****

IDENTIFICATION DIVISION.

PROGRAM-ID. MEM3.

ENVIRONMENT DIVISION.

INPUT-OUTPUT SECTION.

FILE-CONTROL.

SELECT PSFILE ASSIGN TO DD1.

SELECT RRDSFILE ASSIGN TO DD2

ORGANIZATION IS RELATIVE

RELATIVE KEY IS WS-EC

FILE STATUS IS FS1.

DATA DIVISION.

FILE SECTION.

FD PSFILE.

01 PSREC.

02 PS-EC PIC 9(4).

02 PS-EN PIC X(4).

02 FILLER PIC X(72).

FD RRDSFILE.

01 RRDSREC.

02 RS-EC PIC 9(4).

02 RS-EN PIC X(4).

02 FILLER PIC X(72).

WORKING-STORAGE SECTION.

01 WS-DATA.

02 WS-EC PIC 9(4).

02 WS-EN PIC X(4).

77 FS1 PIC X(2).

PROCEDURE DIVISION.

OPEN INPUT PSFILE.

OPEN OUTPUT RRDSFILE.

PERFORM READ-PARA.

READ-PARA.

READ PSFILE AT END CLOSE PSFILE, RRDSFILE

MOVE PSREC TO RRDSREC.

WRITE RRDSREC.

DISPLAY RRDSREC.

GO TO READ-PARA.

STOP RUN.

File Program's in COBOL:

VSAM Program's

noreply@blogger.com (M siva raman) — Tue, 11 Jan 2011 04:41:00 +0000

VSAM PROGRAMS

***** CREATING ESDS CLUSTER *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

DEFINE CLUSTER(NAME(OZA296.SVSAM.ESDS2)-

TRACKS(2,2)-

CISZ(512)-

RECORDSIZE(80 80)-

NONINDEXED)

Vsam for the Cobol Programmer: Concepts, Cobol, Jcl, Idcams

***** CREATING RRDS CLUSTER *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

DEFINE CLUSTER(NAME(OZA296.SVSAM.RRDS1)-

TRACKS(2,2)-

CISZ(512)-

RECORDSIZE(80 80)-

NUMBERED)

***** CREATING KSDS CLUSTER *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

DEFINE CLUSTER(NAME(OZA296.SVSAM.KSDS1)-

KEY(4,0)-

TRACKS(2,2)-

FREESPACE(20,20)-

CISZ(512)-

INDEXED)

***** DELTE COMMAND (Delete the cluster using DELETE command) *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

DELETE OZA296.SVSAM.RRDS1

***** REPRO COMMAND (Coping PS to cluster using REPRO command) *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//DD1 DD DSN=OZA296.SVSAM.PS1,DISP=SHR

//DD2 DD DSN=OZA296.SVSAM.RRDS,DISP=SHR

//SYSIN DD *

REPRO INFILE(DD1) OUTFILE(DD2)

***** ALTER COMMAND (renaming the cluster) *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

ALTER OZA296.SVSAM.ESDS1.DATA-

NEWNAME(OZA296.SVSAM.ESDS2.DATA)

***** CREATING ALTERNATE INDEX *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

DEFINE AIX(NAME(OZA296.SVSAM.KSDS.AIX1)-

RELATE(OZA296.SVSAM.KSDS)-

TRACKS(1 1)-

RECSZ(80 80)-

KEYS(4,7)-

NONUNIQUEKEY-

UPGRADE)

***** BUILD COMMAND (coping from ksds to ksds.aix) *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//DD1 DD DSN=OZA296.SVSAM.KSDS,DISP=SHR

//DD2 DD DSN=OZA296.SVSAM.KSDS.AIX1,DISP=SHR

//SYSIN DD *

BLDINDEX INFILE(DD1)-

OUTFILE(DD2)

***** PATH *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

DEFINE PATH(NAME(OZA296.SVSAM.AIX1.PATH1)-

PATHENTRY(OZA296.SVSAM.KSDS.AIX1))

Creation ESDS Cluster

noreply@blogger.com (M siva raman) — Mon, 10 Jan 2011 12:47:00 +0000

***** CREATING ESDS CLUSTER *****

//OZA296A JOB NOTIFY=&SYSUID

//STEP1 EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

DEFINE CLUSTER(NAME(OZA296.SVSAM.ESDS2)-

TRACKS(2,2)-

CISZ(512)-

RECORDSIZE(80 80)-

NONINDEXED)

Condition Types in Cobol

noreply@blogger.com (M siva raman) — Tue, 04 Jan 2011 10:12:00 +0000

Condition Types

Simple Conditions

Relation Conditions
Class Conditions
Sign Conditions

Complex Conditions
Condition Name

Relation Condition :

Class Condition:

Rules
The target of a class test must be a data-item whose usage is explicitly or implicitly, DISPLAY. In the case of numeric tests, data items with a usage of PACKED-DECIMAL may also be tested.

The numeric test may not be used with data items described as alphabetic (PIC A) or with group items when any of the elementary items specifies a sign.

An alphabetic test may not be used with any data items described as numeric (PIC 9).

An data-item conforms to the UserDefinedClassName if its contents consist entirely of the characters listed in the definition of the UserDefinedClassName.

* Uses the UPPER Intrinsic Function to convert to uppercase

IF InputChar IS ALPHABETIC-LOWER

MOVE FUNCTION UPPER (InputChar) TO InputChar

END-IF

Sign Condition

Complex Condition:

Condition Name Syntax

More than one Condition Names may be true at the same time. For instance, if AgeInYears contains the value 20 both Teenager and Voter will be true.

E.g. 02 AgeInYears  PIC 9(3).

        88 Child    VALUE 0  THRU 12.

        88 Teenager VALUE 13 THRU 19.

        88 Adult    VALUE 21 THRU 999.

        88 Voter    VALUE 18 THRU 999.

1.Sams Teach Yourself COBOL in 24 Hours

2.COBOL for the 21st Century

3.Advanced COBOL for Structured and Object-Oriented Programming, 3rdEdition

Figurative Constants in Cobol

noreply@blogger.com (M siva raman) — Tue, 04 Jan 2011 07:35:00 +0000

Figurative Constants:

Unlike most other programming languages COBOL does not provide a mechanism for creating user-defined constants but it does provide a set of special constants called Figurative Constants.
A Figurative Constant may be used wherever it is legal to use a literal but unlike literals, when a Figurative Constant is assigned to a data-item it fills the whole item overwriting everything in it.

The Figurative Constants are:

· SPACE or SPACES Acts like one or more spaces

· ZERO or ZEROS or ZEROES Acts like one or more zeros

· QUOTE or QUOTES Used instead of a quotation mark

· HIGH-VALUE or HIGH-VALUES Uses the maximum value possible

· LOW-VALUE or LOW-VALUES Uses the minimum value possible

· ALL literal Allows a ordinary literal to act as Figurative Constant

Isolation level in DB2

noreply@blogger.com (M siva raman) — Fri, 31 Dec 2010 04:47:00 +0000

1.SERIALIZABLE(Repeatable read (RR))

2.REPEATABLE READ(Read stability (RS))

3.READ COMMITTED(Cursor stability (CS)) (default)

4.READ UNCOMMITTED(Uncommitted read (UR))

SERIALIZABLE (DB2 UDB: Repeatable Read)

Locks the table within a unit of work. An application can retrieve and operate on rows in the table as many times as needed. However, the entire table is locked, not just the rows that are retrieved. Until the unit of work completes, no other application can update, delete, or insert a row that would affect the table.

SERIALIZABLE applications cannot see uncommitted changes made by other applications. Therefore, a SELECT statement issued repeatedly within the unit of work gives the same result each time. Lost updates, access to uncommitted data, and phantom rows are not possible.

REPEATABLE READ (DB2 UDB: Read Stability)

Because DB2 Everyplace locks entire tables (not specific rows), REPEATABLE READ behaves exactly like SERIALIZABLE.

READ COMMITTED (DB2 UDB: Cursor Stability)

The entire table is locked. Shared locks are released when the associated cursors are closed (isolation levels higher than READ COMMITTED hold shared locks until the end of a transaction). Exclusive locks are held until the end of the transaction.

No other application can perform any DML operation on a table while an open cursor is accessing it. READ COMMITTED applications cannot see uncommitted changes of other applications.

Both nonrepeatable reads and phantom reads are possible. READ COMMITTED is the default isolation level, allowing maximum concurrency while seeing only committed rows from other applications.

READ UNCOMMITTED (DB2 UDB: Uncommitted Read)

An application can access some uncommitted changes of other transactions: tables and indexes that are being created or dropped by other transactions are not available while the transaction is processing. Any other changes can be read before they are committed or rolled back.

At this level, the application does not lock other applications out of the table it is reading.

DB2 FAQ's

noreply@blogger.com (M siva raman) — Mon, 27 Dec 2010 07:41:00 +0000

DB2 FAQS

1. How would you find out the total number of rows in a table?

o Use SELECT COUNT(*) ...

2. How do you eliminate duplicate values in SELECT?

o Use SELECT DISTINCT ...

3. How do you select a row using indexes?

o Specify the indexed columns in the WHERE clause.

4. What are aggregate functions?

o Built-in mathematical functions for use in SELECT clause.

5. How do you find the maximum value in a column?

o Use SELECT MAX(...)

6. Can you use MAX on a CHAR column?

o Yes.

7. My SQL statement SELECT AVG(SALARY) FROM EMP yields inaccurate results. Why?

o Because SALARY is not declared to have NULLs and the employees for whom the salary is not known are also counted.

8. How do you retrieve the first 5 characters of FIRSTNAME column of EMP table?

o SELECT SUBSTR(FIRSTNAME,1,5) FROM EMP;

9. How do you concatenate the FIRSTNAME and LASTNAME from EMP table to give a complete name?

o SELECT FIRSTNAME ¦¦ ' ' ¦¦ LASTNAME FROM EMP;

10. What is the use of VALUE function?

o Avoid -ve SQLCODEs by handling nulls and zeroes in computations

o Substitute a numeric value for any nulls used in computation

11. What is UNION,UNION ALL?

o UNION : eliminates duplicates
UNION ALL: retains duplicates
Both these are used to combine the results of different SELECT statements.

12. Suppose I have five SQL SELECT statements connected by UNION/UNION ALL, how many times should I specify UNION to eliminate the duplicate rows?

o Once.

13. What is the restriction on using UNION in embedded SQL?

o It has to be in a CURSOR.

14. In the WHERE clause what is BETWEEN and IN?

o BETWEEN supplies a range of values while IN supplies a list of values.

15. Is BETWEEN inclusive of the range values specified?

o Yes.

16. What is 'LIKE' used for in WHERE clause? What are the wildcard characters?

o LIKE is used for partial string matches. '%' ( for a string of any character ) and '_' (for any single character ) are the two wild card characters.

17. When do you use a LIKE statement?

o To do partial search e.g. to search employee by name, you need not specify the complete name; using LIKE, you can search for partial string matches.

18. What is the meaning of underscore ( '_' ) in the LIKE statement?

o Match for any single character.

19. What do you accomplish by GROUP BY ... HAVING clause?

o GROUP BY partitions the selected rows on the distinct values of the column on which you group by.

o HAVING selects GROUPs which match the criteria specified

20. Consider the employee table with column PROJECT nullable. How can you get a list of employees who are not assigned to any project?

o SELECT EMPNO
FROM EMP
WHERE PROJECT IS NULL;

21. What is the result of this query if no rows are selected:

o SELECT SUM(SALARY)
FROM EMP
WHERE QUAL='MSC';
NULL

22. Why SELECT * is not preferred in embedded SQL programs?

o For three reasons:

1. If the table structure is changed ( a field is added ), the program will have to be modified.

2. Program might retrieve the columns which it might not use, leading on I/O over head.

3. The chance of an index only scan is lost.

23. What are correlated sub queries?

o A sub query in which the inner ( nested ) query refers back to the table in the outer query. Correlated sub queries must be evaluated for each qualified row of the outer query that is referred to.

24. What is a cursor? why should it be used?

o Cursor is a programming device that allows the SELECT to find a set of rows but return them one at a time.

o Cursor should be used because the host language can deal with only one row at a time.

25. How would you retrieve rows from a DB2 table in embedded SQL?

o Either by using the single row SELECT statements, or by using the CURSOR.

26. Apart from cursor, what other ways are available to you to retrieve a row from a table in embedded SQL?

o Single row SELECTs.

27. How do you specify and use a cursor in a COBOL program?

o Use DECLARE CURSOR statement either in working storage or in procedure division (before open cursor), to specify the SELECT statement. Then use OPEN, FETCH rows in a loop and finally CLOSE.

28. What happens when you say OPEN CURSOR?

o If there is an ORDER BY clause, rows are fetched, sorted and made available for the FETCH statement. Other wise simply the cursor is placed on the first row.

29. Is DECLARE CURSOR executable?

o No.

30. Can you have more than one cursor open at any one time in a program?

o Yes.

31. When you COMMIT, is the cursor closed?

o Yes.

32. How do you leave the cursor open after issuing a COMMIT? (for DB2 2.3 or above only )

o Use WITH HOLD option in DECLARE CURSOR statement. But, it has not effect in psuedo-conversational CICS programs.

33. Give the COBOL definition of a VARCHAR field.

o A VARCHAR column REMARKS would be defined as follows:

10 REMARKS.

49 REMARKS-LEN PIC S9(4) USAGE COMP.

49 REMARKS-TEXT PIC X(1920).

34. What is the physical storage length of each of the following DB2 data types: DATE, TIME, TIMESTAMP?

DATE:	4bytes
TIME:	3bytes
TIMESTAMP:	10bytes

35. What is the COBOL picture clause of the following DB2 data types: DATE, TIME, TIMESTAMP?

DATE:	PIC X(10)
TIME :	PIC X(08)
TIMESTAMP:	PIC X(26)

36. What is the COBOL picture clause for a DB2 column defined as DECIMAL(11,2)?

o PIC S9(9)V99 COMP-3.
Note: In DECIMAL(11,2), 11 indicates the size of the data type and 2 indicates the precision.

37. What is DCLGEN?

o DeCLarations GENerator: used to create the host language copybooks for the table definitions. Also creates the DECLARE table.

38. What is JOIN and different types of JOIN.

o The ability to join rows and combine data from two or more tables is one of the most powerful features of relational system. Three types of joins:

1. Equi-join

2. Non-equijoin

3. self-join

39. Can I alter a table (e.g. adding a column) when other user is selecting some Columns or updating some columns from the same table?

o yes possible. until the updation or selection is committed db2 table will not be restructured. new column definition will be there but it will not be included until all the tasks on the table are committed.

40. What are the different methods of accessing db2 from tso?

o There are three ways in establishing tso/db2 connection

1. SPUFI

2. QMF

3. CATALOG VISIBILITY

41. How is the connection established between TSO & DB2?

o A thread between TSO & DB2 is established while attempting to make Connection between tso & db2.

42. What is sqlcode -922?

o Authorization failure

43. How do you do the EXPLAIN of a dynamic SQL statement?

o Use SPUFI or QMF to EXPLAIN the dynamic SQL statement

o Include EXPLAIN command in the embedded dynamic SQL statements

44. How is a typical DB2 batch pgm executed?

o Use DSN utility to run a DB2 batch program from native TSO. An example is shown:

DSN	SYSTEM(DSP3)
RUN	PROGRAM(EDD470BD) PLAN(EDD470BD)
LIB	('EDGS01T.OBJ.LOADLIB')
END

o Use IKJEFT01 utility program to run the above DSN command in a JCL.

45. Is it mandatory to use DCLGEN? If not, why would you use it at all?

o It is not mandatory to use DCLGEN.
Using DCLGEN, helps detect wrongly spelt column names etc. during the
pre-compile stage itself (because of the DECLARE TABLE ).
DCLGEN being a tool, would generate accurate host variable definitions for the table reducing chances of error.

46. Name some fields from SQLCA.

o SQLCODE, SQLERRM, SQLERRD

47. How does DB2 determine what lock-size to use?

o Based on the lock-size given while creating the table space

o Programmer can direct the DB2 what lock-size to use

o If lock-size ANY is specified, DB2 usually choses a lock-size of PAGE

48. What is the difference between CS and RR isolation levels?

o CS: Releases the lock on a page after use

o RR: Retains all locks acquired till end of transaction

49. Where do you specify them?

o ISOLATION LEVEL is a parameter for the bind process.

50. How do you simulate the EXPLAIN of an embedded SQL statement in SPUFI/QMF? Give an example with a host variable in WHERE clause.

o Use question mark in place of a host variable (or an unknown value). e.g.

SELECT EMP_NAME
FROM EMP
WHERE EMP_SALARY > ?

51. What is ACQUIRE/RELEASE in BIND?

o Determine the point at which DB2 acquires or releases locks against table and Table spaces, including intent locks.

52. In SPUFI suppose you want to select max. of 1000 rows, but the select returns only 200 rows. What are the 2 sqlcodes that are returned?

o 100 (for successful completion of the query), 0 (for successful COMMIT if AUTOCOMMIT is set to Yes).

53. How would you print the output of an SQL statement from SPUFI?

o Print the output data set.

54. What does it mean if the null indicator has -1, 0, -2?

o -1 : the field is null

o 0 : the field is not null

o -2 : the field value is truncated

55. How do you retrieve the data from a nullable column?

o Use null indicators. Syntax ... INTO :HOSTVAR:NULLIND

56. What else is there in the PLAN apart from the access path?

o PLAN has the executable code for the SQL statements in the host program

57. What is lock escalation?

o Promoting a PAGE lock-size to table or table space lock-size when a transaction has aquired more locks than specified in NUMLKTS. Locks should be taken on objects in single table space for escalation to occur.

58. When is the access path determined for dynamic SQL?

o At run time, when the PREPARE statement is issued.

59. What are the various locks available?

o SHARE, EXCLUSIVE, UPDATE

60. What is sqlcode -811?

o SELECT statement has resulted in retrieval of more than one row.

61. What are the advantages of using a PACKAGE?

o Avoid having to bind a large number of DBRM members into a plan

o Avoid cost of a large bind

o Avoid the entire transaction being unavailable during bind and automatic rebind of a plan

o Minmize fallback complexities if changes result in an error.

62. What is REORG? When is it used?

o REORG reorganizes data on physical storage to re-cluster rows, positioning oveflowed rows in their proper sequence, to reclaim space, to restore free space. It is used after huge updates, inserts and delete activity and after segments of a segmented table space have become fragmented.

63. How does DB2 store NULL physically?

o as an extra-byte prefix to the column value. physically, the nul prefix is Hex '00' if the value is present and Hex 'FF' if it is not

64. What is CHECK PENDING?

o When a table is LOADed with ENFORCE NO option, then the table is left in CHECKPENDING status. It means that the LOAD utility did not perform constraint checking.

65. When do you specify the isolation level? How?

o During the BIND process. ISOLATION (CS/RR)...

66. What is a DBRM, PLAN?

o DBRM: DataBase Request Module, has the SQL statements extracted from the host language program by the pre-compiler.

o PLAN: A result of the BIND process. It has the executable code for the SQL statements in the DBRM.

67. Is DECLARE TABLE in DCLGEN necessary? Why it used?

o It not necessary to have DECLARE TABLE statement in DCLGEN. This is used by the pre-compiler to validate the table-name, view-name, column name etc., during pre-compile.

68. What do you need to do before you do EXPLAIN?

o Make sure that the PLAN_TABLE is created under the AUTHID.

69. What is a collection?

o a user defined name that is the anchor for packages. It has not physical existence. Main usage is to group packages.

70. How can you quickly find out the # of rows updated after an update statement?

o Check the value stored in SQLERRD(3).

71. What is EXPLAIN?

o EXPLAIN is used to display the access path as determined by the optimizer for a SQL statement. It can be used in SPUFI (for single SQL statement ) or in BIND step (for embedded SQL ).

72. Where is the output of EXPLAIN stored?

o In userid.PLAN_TABLE

73. Suppose I have a program which uses a dynamic SQL and it has been performing well till now. Off late, I find that the performance has deteriorated. What happened?

o Probably RUN STATS is not done and the program is using a wrong index due to incorrect stats. Probably RUNSTATS is done and optimizer has chosen a wrong access path based on the latest statistics.

74. What are the contents of a DCLGEN? - GS

o EXEC SQL DECLARE TABLE statement which gives the layout of the table/view in terms of DB2 data types.

o A host language copy book that gives the host variable definitions for the column names.

75. Will pre-compile of an DB2-COBOL program bomb, if DB2 is down?

o No. Because the pre-compiler does not refer to the DB2 catalogue tables.

76. What are the isolation (also called isolation parameters) levels possible?

o CS: Cursor Stability

o RR: Repeatable Read

77. What is the picture clause of the null indicator variable?

o S9(4) COMP.

78. EXPLAIN has output with MATCHCOLS = 0. What does it mean?

o A non-matching index scan if ACCESSTYPE = I.

79. I use CS and update a page. Will the lock be released after I've done with that page?

o No.

80. What are the various locking levels available?

o PAGE, TABLE, TABLESPACE

81. What is ALTER?

o SQL command used to change the definition of DB2 objects.

82. Can I use LOCK TABLE on a view?

o No. To lock a view, take lock on the underlying tables.

83. What are the disadvantages of PAGE level lock?

o High resource utilization if large updates are to be done

84. What are PACKAGES ?

o They contain executable code for SQL statements for one DBRM.

85. Lot of updates have been done on a table due to which indexes have gone haywire. What do you do?

o Looks like index page split has occured. DO a REORG of the indexes.

86. What is dynamic SQL?

o Dynamic SQL is a SQL statement created at program execution time.

87. What is IMAGECOPY ?

o It is full backup of a DB2 table which can be used in recovery.

88. What is QUIESCE?

o A QUIESCE flushes all DB2 buffers on to the disk. This gives a correct snapshot of the database and should be used before and after any IMAGECOPY to maintain consistency.

89. What does the sqlcode of -818 pertain to? - GS

o This is generated when the consistency tokens in the DBRM and the load module are different.

90. What happens to the PLAN if index used by it is dropped?

o Plan is marked as invalid. The next time the plan is accessed, it is rebound.

91.

92. What is FREEPAGE and PCTFREE in TABLESPACE creation?

o PCTFREE: percentage of each page to be left free

o FREEPAGE: Number of pages to be loaded with data between each free page

93. Are views updatable?

o Not all of them. Some views are updatable e.g. single table view with all the fields or mandatory fields. Examples of non-updatable views are views which are joins, views that contain aggregate functions (such as MIN), and views that have GROUP BY clause.

94. What is COPY PENDING status?

o A state in which, an image copy on a table needs to be taken, in this state, the table is available only for queries. You cannot update this table. To remove the COPY PENDING status, you take an image copy or use REPAIR utility.

95. What is an inner join, and an outer join?

o Inner Join: combine information from two or more tables by comparing all values that meet the search criteria in the designated column or columns of one table with all the values in corresponding columns of the other table or tables. This kind of join which involve a match in both columns are called inner joins.

o Outer join is one in which you want both matching and non matching rows to be returned. DB2 has no specific operator for outer joins, it can be simulated by combining a join and a correlated sub query with a UNION.

96.

97. What is the difference between primary key & unique index?

o Primary: a relational database constraint. Primary key consists of one or more columns that uniquely identify a row in the table. For a normalized relation, there is one designated primary key.

o Unique index: a physical object that stores only unique values. There can be one or more unique indexes on a table.

98. When do you use the IMAGECOPY?

o To take routine backup of tables.

o After a LOAD with LOG NO. After REORG with LOG ON.

99. What is RUNSTATS?

o A DB2 utility used to collect statistics about the data values in tables which can be used by the optimizer to decide the access path. It also collects statistics used for space management. These statistics are stored in DB2 catalog tables.

100. How do you insert a record with a nullable column?

o To insert a NULL, move -1 to the null indicator

o To insert a valid value, move 0 to the null indicator