Tag: technology

Inner Join

Explicit Join ( record-required 0 = true, record-required 1 = true )

Explicit Join ( record-required 0 = false, record-required 1 = true )

Explicit Join ( record-required 0 = true, record-required 1 = false )

Library Division

Environment Division & Activity Division

Activity Division

None of the above

RECORD-LENGTH(DDName)

RECLEN(DDName)

RECLN(DDName)

It is not possible in Easytrieve

EVALUATE … END-EVALUATE

SWITCH CASE

CASE … END-CASE

None of the above

MATCH cannot be used on multiple files

MATCH can be used on multiple files

MATCH can be used when key is defined

MATCH can be used with JOB statement

GET

PUT

READ

POINT

Compile listing in Easytrieve cannot be produced

Data map alone can be produced

Compile listing alone can be produced

Data map and Compile listing can be produced using DMAP and PMAP option in DEBUG

Both State-Code and Account-Entity refer to the 16th byte of the Account-Recored

This definition would throw invalid referencing error while executing

Account-Number refers to the 10th byte of Account-Record

Account-Entity refers to the 15th byte of the Account-Record

This statement is used to copy record from PERSNL to MYFILE if the entire record is identical in both the files

This statement moves the like named field values from PERSNL to MYFILE

This statement moves the record from PERSNL to MYFILE if the record-length matches

Both a & c are correct

The POINT statement will only establish the position within an ISAM, VSAM relative record (RRDS), VSAM (KSDS) indexed file.

Data in the file will be available only after the next successful sequential retrieval by a file input statement.

both a & b

None of the above