Packed datasets

Packed data is data in which ISPF has replaced any repeating characters with a sequence showing how many times the character is repeated. Packing data allows you to use direct access storage devices (DASD) more efficiently because the stored data occupies less space than it would otherwise.

If the source data that you want to process is packed, it must be expanded before it can be successfully processed by any of the language processors. The expansion method you should use depends on whether your source data is:

=>A sequential dataset that contains expansion triggers:

An expansion trigger is a keyword that tells ISPF to expand additional data before copying, including or imbedding it in the source data. ISPF does not recognise expansion triggers in data stored as a sequential dataset. Therefore, for these types of datasets,

1. Manually expand the data: Edit the source data and enter PACK OFF
2. Select the Source Data Packed option before calling one of the language processors.

=>Either of the following:
A. A Sequential dataset that does not contain expansion triggers
B. Any member of a partitioned dataset, either with or without expansion triggers.

ISPF does recognize expansion triggers in data stored as members of a partitioned data set. Also, if your source data does not contain expansion triggers, you do not have to be concerned with them. Therefore, for these two types of data, select the Source Data Packed option before calling one of the language processors.

Abend S013

Could be one of the following reasons:

->Conflicting or incomplete parameters in DCB, such as BLKSIZE not a multiple of LRECL, or
missing SYSIN DD;
->Tried to create a PDS without allocating directory blocks;
->Member name specified in DD not found;
->no directory allocation sub parameter in DD;
->Open output dataset as input;
->Track overflow or updating attempted, but not supported by the OS.
->May be a record length or OPEN statement error.

SQLCODE = -204

ERROR: is an undefined name

SQLCODE = -679

Error: The object cannot be created because a drop is pending on the object. This occurred

when a create index statement is issued immediately after a drop index statement.

Drop index
create index on
(col1 Asc, Col2 Asc);
Commit work;

SQL : Error handling : WHENEVER stmt

The WHENEVER statment specifies the action to be taken when a specified exception condition occurs
This stmt can only be empedded in an application program. It is not an exeuctable stmt. It must not be specified in Java or REXX.

Syntax:
WHENEVER <>

Default :
WHENEVER <> CONTINUE.