IDSTPRDD03 - Duplicate end delimiter line found

Source Transport (SR) Messages › › IDSTPRDD03 - Duplicate end delimiter line found

Reason:

The trailer ->END-entity was encountered more than once before a new entity-header was encountered on the external source file.

Action:

If external source is unmodified from a single EXPORT, contact CA Technical Support. For information to facilitate your call, see the Problem Determination Guide. If you created or modified the external source, check the spelling and syntax of external source up to the source line indicated by the message. Re-specify and reIMPORT after correcting errors.

IDSTPRDD04 - Command not produced due to invalid start delimiter

Reason:

The Source Transport utility was expecting a new start-entity header. The input record just read was not a valid start-entity header. Records are skipped until the next end-entity trailer record is sensed, if SET ERROR CONTINUE is in force. Otherwise, execution of Source Transport terminates.

Action:

Correct the errors and re-specify.

IDSTPRDD05 - Number IMPORT PROGRAM commands have been produced

Reason:

The message is self-explanatory.

Action:

None.

IDSTPRDD06 - Number IMPORT PANEL commands have been produced

Reason:

The message is self-explanatory.

Action:

None.

IDSTPRDD07 - Number IMPORT REPORT commands have been produced

Reason:

The message is self-explanatory.

Action:

None.

IDSTPRDD08 - Number IMPORT MEMBER commands have been produced

Reason:

The message is self-explanatory.

Action:

None.

IDSTPRDD09 - Number IMPORT DATAVIEW commands have been produced

Reason:

The message is self-explanatory.

Action:

None.

IDSTPRDD10 - Number IMPORT commands in total have been produced

Reason:

The message is self-explanatory.

Action:

None.

IDSTPRDD11 - No IMPORT commands have been produced

Reason:

The message is self-explanatory.

Action:

Correct the errors and re-specify.

IDSTPRDD12 - Number duplicate entities found on IMPORT dataset

Reason:

The external source data contains the same entity more than once. This could have happened, for instance, if the output of two separate EXPORT runs were concatenated into a single external source file, and if each of the constituent runs separately exported the same entity.

Action:

None.

IDSTPRDD13 - Invalid delimiters found on IMPORT dataset

Reason:

Action:

None.

IDSTPRDD14 - PRODUCE operation aborted due to a system error

Reason:

An unexpected or unusual condition terminated a CA Ideal command or run-time application.

Action:

Contact CA Technical Support. For information to facilitate your call, see the Problem Determination Guide.

IDSTPRDD15 - PRODUCE operation successfully completed

Reason:

The IMPORT process successfully terminated with no warnings or errors issued.

Action:

None.

IDSTPRDD16 - PRODUCE operation completed. Warnings were issued.

Reason:

The IMPORT process successfully terminated, but warnings were issued for individual entities processed.

Action:

No action is required. You should ensure that the condition that caused the warning does not occur at run-time, since run-time errors or other unexpected results could occur.

IDSTPRDD17 - PRODUCE operation completed. Errors were detected.

Reason:

The IMPORT process successfully terminated, but errors and warnings were issued for individual entities processed.

Action:

Correct the errors and re-specify.

IDSTRPTE01 - IDSTRPTE04

IDSTRPTE01 - Report in use, please try later

Reason:

Another CA Ideal session is using the entity named, online or in batch. Underlying causes of this problem include:

Another user is actually accessing the entity. The access that the other user is performing requires that the entity not be shared or altered as required in your session.
You yourself can be the other user, if you are editing online for instance, and attempting to perform another manipulation in batch that must also retain control of the entity. This can also occur when operating in split-screen mode, where your CA Ideal screen's two regions act as different CA Ideal sessions.
An ABEND in a CA Ideal session left an outstanding enqueue on the named entity.
An enqueue against this entity exists in another region and a unique QCODE was not specified.

Action:

Determine which of the above causes was involved and take appropriate action:

Have the users interfering with your command relinquish control. Otherwise, wait until the affected entity is no longer in use.
End activities of your own that conflict with your intended use of the entity.
See your administrator to DEQUEUE outstanding enqueues against the entity still left in force because of previous abended CA Ideal tasks.
See the CA IPC Implementation Guide for information on specifying unique enqueue names across systems.

IDSTRPTE02 - Report not found

Reason:

The report specified cannot be found in the current system.

Action:

Check that the report name is correct and spelled correctly. Check that the EXPORT SYSTEM was properly SET or properly specified in the EXPORT command. Make appropriate changes as necessary to the Source Transport command stream.

IDSTRPTE03 - Prior abend (USR short-user-id active)

Reason:

While USER short-user-id was performing an edit session, an abend occurred. CA Ideal does not permit EXPORT of a report in this state.

Action:

Edit the report with either the CHECKPOINT or ROLLBACK commands issued during the edit session to resolve the abend. Repeat the EXPORT after the edit is successfully completed.

IDSTRPTE04 - More than five text lines found. Only five have been exported

Reason:

CA Ideal Source Transport utility supports up to 5 lines of text being EXPORTed for an entity, conforming to the requirements of the CA Ideal IDENTIFICATION subsystem editor. The utility does not support transport of dictionary text that does not conform to a format that is usable to CA Ideal editors.

Action:

Use the Datadictionary Backup and Transport utility (BTG) to transport text created by direct Datadictionary modification, the only way such non-standard text could be entered.

IDSTRPTI01 - IDSTRPTI27

IDSTRPTI01 - Source data invalid or incomplete starting at “word”

Reason:

You entered a command that violates the command syntax starting at the specified word.

Action:

IDSTRPTI02 - Source data contains an invalid keyword

Reason:

You entered an item into external source for an EXPORTed entity where the IMPORT logic expected a valid keyword. This can happen, for instance, if the previous keyword requires a quoted string as an operand but quotation marks or apostrophes were not properly used to enclose the quoted string.

Action:

IDSTRPTI03 - INTERR: Command parser stack overflow

Reason:

You entered a Source Transport entity-definition that the CA Ideal command parser could not interpret into external source data.

Action:

IDSTRPTI04 - INTERR: Repetition problem in command parser

Reason:

An internal error occurred in the Source Transport entity-parser.

Action:

Contact CA Technical Support. For information to facilitate your call, see the Problem Determination Guide.

IDSTRPTI05 - VERSION number must be between 1 and 999

Reason:

The VERSION number supplied on the entity header was not in the required range.

Action:

IDSTRPTI06 - Unexpected END-OF-FILE reached

Reason:

The EXTSRC external source data ended before the trailer ->END-entity was sensed to end the processing of the current input.

Action:

IDSTRPTI07 - INTERR: Columnar data word error

Reason:

Columnar data did not conform to the expected format or invalid values were present in the columnar data. The column-name where the format was first detected was word; however, this can indicate:

Corruption in previous columns of the same record
Missing ->sub-entity-DATA header (to designate a change in columnar-data format for the next sub-entity)
Missing ->END-entity trailer (to designate the end of columnar data for the last sub-entity)

Action:

IDSTRPTI08 - short-system-id is not a valid SYSTEM

Reason:

The SYSTEM short-id provided on the external source data set is not valid for the IMPORTing environment. This error should only occur with NEW SYSTEM ASIS in force for the IMPORT being executed.

Action:

Several courses of action are possible to correct this error:

Define the invalid system to CA Ideal for the IMPORTing environment.
Specify a NEW SYSTEM for the IMPORT command that caused the error with a valid short-system-id for the IMPORTing environment.
Modify the external source data set so that the system-short-id in the offending entity is a valid one for the IMPORTing environment.

IDSTRPTI09 - Numeric operand "number" has too many digits

Reason:

The number specified in the command exceeds 18 digits.

Action:

Change the numeric operand so the number contains 1 to 18 digits.

IDSTRPTI10 - Operand “word” may not exceed number characters

Reason:

The operand specified exceeds the maximum allowable number of characters.

Action:

Enter a value for the operand that does not exceed number characters.

IDSTRPTI11 - Duplicate keyword found, data "KEYWORD operand" ignored

Reason:

The keyword was found more than once for a single entity in the external source data for the same entity. Only the data from the first occurrence of the keyword is used, additional occurrences of the keyword have their data ignored.

Action:

If external source is unmodified from an EXPORT, contact CA Technical Support. For information to facilitate your call, see the Problem Determination Guide. If you created or modified the external source, check spelling and syntax of external source up to the source line indicated by the message. Verify that the data in the first occurrence of the keyword was the appropriate data in the newly IMPORTed entity. Re-specify the external source and reIMPORT if necessary.

IDSTRPTI12 - Entity must be in test status to be REPLACED

Reason:

Action:

Several courses of action are possible to achieve a successful IMPORT:

Alter the IMPORTing environment with CA Ideal to delete entities that would cause duplicates when the entity is IMPORTed.
Alter the operands of the IMPORT, either through explicit command specification or through implicit SET commands, so that NEW VERSION NEXT is in effect for the offending entity.
Alter the SET IMPORT DUPLICATE operand so that NEXT VERSION is in effect.

IDSTRPTI13 - One or more syntax errors encountered

Reason:

One or more syntax errors in the external source data for this entity were encountered. Such errors are noted in previous messages listed while processing this entity.

Action:

If external source is unmodified from a single EXPORT, contact CA Technical Support. For information to facilitate your call, see the Problem Determination Guide. If you created or modified the external source, check the spelling and syntax of external source up to the source line indicated by the message. Re-specify and reIMPORT after correcting errors.

IDSTRPTI14 - Report report-name is in use, please try later

Reason:

The IMPORT of the current entity duplicates an existing entity in the IMPORTing environment, which is not in TEST status. The setting of SET IMPORT DUPLICATE for this run of Source Transport was REPLACE; but REPLACEment could not proceed because the program (of the IMPORTing environment) was in use by another user.

Action:

Determine which of the above causes was involved and take appropriate action:

Have the users interfering with your command relinquish control. Otherwise, wait until the affected entity is no longer in use.
End activities of your own that conflict with your intended use of the entity.
See your administrator to DEQUEUE outstanding enqueues against the entity still left in force because of previous abended CA Ideal tasks.
See the CA IPC Implementation Guide for information on specifying unique enqueue names across systems.

IDSTRPTI15 - Report report-name already exists - IMPORT terminated

Reason:

Action:

Several courses of action are possible to achieve a successful IMPORT:

Alter the IMPORTing environment with CA Ideal to delete entities that would cause duplicates when the entity is IMPORTed.
Alter the operands of the IMPORT, either through explicit command specification or through implicit SET commands, so that NEW VERSION NEXT is in effect for the offending entity.
Alter the SET IMPORT DUPLICATE operand so that NEXT VERSION is in effect.

IDSTRPTI16 - Report report-name already exists - IMPORT skipped

Reason:

The IMPORT of the current entity duplicates an existing entity in the IMPORTing environment, which is not in TEST status. The setting of SET IMPORT DUPLICATE for this run of Source Transport was SKIP. No error resulted. This message is a warning only. Should you decide you must import the skipped entity, corrective action might be needed; however, no action is required.

Action:

Several courses of action are possible to achieve a successful IMPORT:

Alter the IMPORTing environment with CA Ideal to delete entities that would cause duplicates when the entity is IMPORTed.
Alter the operands of the IMPORT, either through explicit command specification or through implicit SET commands, so that NEW VERSION NEXT is in effect for the offending entity.
Alter the SET IMPORT DUPLICATE operand so that NEXT VERSION is in effect.

IDSTRPTI17 - Report status on import tape ignored

Reason:

The report is stored on the EXTSRC data set with a status other than TEST, but when IMPORT is complete, status is TEST.

Action:

To achieve the status specified on the EXTSRC data set, MARK STATUS as needed. Compile associated programs to assure that no changes are necessary in the report before the MARK STATUS commands.

IDSTRPTI18 - Export release number greater than import release release-number

Reason:

The Source Transport utility software was developed for release release-number. External source data generated for a later release might not be compatible with this release of Source Transport utility.

Action:

This is a warning only, so no action is necessary. Should additional activity be needed, the following courses of action might be appropriate:

Obtain the downgrade zaps for release release-number. Perform the IMPORT with the same release of the utility as was used in the EXPORTing environment. The upgraded format for the IMPORTed modules should now be compatible with the lower release subsystem editors and compiler.
ReEXPORT the entities for the later release, using the lower release release-number version of CA Ideal Source Transport. The IMPORT for release release-number source should now succeed without error.
Alter the external source data to remove added features of the later release, which cannot be processed by release release-number CA Ideal. Change the release-number after the keyword Ideal to be identical with the release expected in the IMPORTing environment.

IDSTRPTI19 - ->HEADING-DATA delimiter line contains extra data

Reason:

The delimiter should contain only spaces after the keyword ->subentity-DATA in columns 1-72, but non-space extra data was found. This is only a warning.

Action:

Although this situation is not serious, it can indicate corruption of the external source data set, particularly if unmodified from a recent EXPORT. If external source is unmodified from an EXPORT, but such corruption is detected, contact CA Technical Support. For information to facilitate your call, see the Problem Determination Guide. If you created or modified external source, check the spelling and syntax of external source up to the source line indicated by the message. Re-specify and reIMPORT after correcting errors.

IDSTRPTI20 - ->DETAIL-DATA delimiter line contains extra data

Reason:

The delimiter should contain only spaces after the keyword ->subentity-DATA in columns 1-72, but non-space extra data was found. This is only a warning.

Action:

IDSTRPTI21 - Expected numeric operand, found word

Reason:

The operand word contains non-numeric characters.

Action:

IDSTRPTI22 - Columnar data has data in columns that must be blank

Reason:

Columnar data did not conform to the expected format. Invalid values were present in the columnar data where only spaces were expected. This can indicate:

Corruption in previous columns of the same record
Missing ->sub-entity-DATA header (to designate a change in columnar-data format for the next sub-entity)
Missing ->END-entity trailer (to designate the end of columnar data for the last sub-entity)

Action:

IDSTRPTI23 - No user heading record after detail record with "U" in col 46

Reason:

When a Report-Detail columnar data record contains a U (user-supplied column heading) in column 46, the next data record must contain an H in column 1 and a space in column 2. This continuation-record supplies the associated user-supplied column-heading. If the expected continuation is not present when the U is specified in column 46 of the detail, an error results.

Action:

IDSTRPTI24 - User heading record after detail record without "U" in col 46

Reason:

When a Report-Detail columnar data record contains a U (user-supplied column heading) in column 46, the next data record must contain an H in column 1 and a space in column 2. This continuation-record supplies the associated user-supplied column-heading. Conversely, if a continuation is found for a report-detail that did not have a U in column 46, then there must be an error.

Action:

IDSTRPTI25 - Detail record must have blank or "H" in column 1

Reason:

Columnar data did not conform to the expected format or invalid values were present in the columnar data. This can indicate:

Corruption in previous columns of the same record
Missing ->sub-entity-DATA header (to designate a change in columnar-data format for the next sub-entity)
Missing ->END-entity trailer (to designate the end of columnar data for the last sub-entity)

Action:

IDSTRPTI26 - Found "item" where an alpha literal was expected

Reason:

An alphanumeric literal enclosed in apostrophes (') or quotation marks (") was expected. The alphanumeric literal was either omitted or its quotes were not properly employed to delimit the literal.

Action:

IDSTRPTI27 - Invalid value for KEYWORD operand

Reason:

The keyword of the message contains an invalid operand.

Action:

IDSTSETC01 - IDSTSETC99

IDSTSETC01 - Command invalid or incomplete starting at “word”

Reason:

You entered a command that violates the command syntax starting at the specified word.

Action:

Check the spelling and command syntax.

IDSTSETC02 - Command contains an invalid special character

Reason:

You entered a special character into a command that violates the command syntax.

Action:

Check the command syntax. Correct the errors and re-specify.

IDSTSETC03 - INTERR: Command parser stack overflow

Reason:

You entered a CA Ideal command that the command parser could not interpret.

Action:

Attempt to simplify the command. If this does not work, determine exactly which command caused the problem and contact CA Technical Support.

IDSTSETC04 - INTERR: Repetition problem in command parser

Reason:

An internal error occurred in the CA Ideal command parser.

Action:

Contact CA Technical Support. For information to facilitate your call, see the Problem Determination Guide.

IDSTSETC06 - INTERR: Service not available

Reason:

The requested service is not available in the CA Ideal command parser.

Action:

Contact CA Technical Support. For information to facilitate your call, see the Problem Determination Guide.

IDSTSETC07 - INTERR: Service not yet ready

Reason:

The requested service could not be completed in the CA Ideal command parser.

Action:

Contact CA Technical Support. For information to facilitate your call, see the Problem Determination Guide.

IDSTSETC10 - "VER nnn" (specific number) must follow entity name

Reason:

This command requires a version number. PROD, HIST, and LAST cannot be used in this command.

Action:

Add the version clause following the entity name.

IDSTSETC12 - Numeric operand "number" has too many digits

Reason:

The number specified in the command has more than 18 digits.

Action:

Change the numeric operand so the number contains 1 to 18 digits.

IDSTSETC13 - Numeric operand "number" exceeds maximum value

Reason:

The number entered in the command exceeds the maximum value that can be processed (2,147,483,647).

Action:

Reduce the magnitude of the number and try again.

IDSTSETC14 - Operand “word” may not exceed num characters

Reason:

The operand specified exceeds the maximum allowable number of characters.

Action:

Reduce the number of characters in the operand.

IDSTSETC17 - VERSION must be 1 through 999, PROD or T1 through T999

Reason:

The version number specified for a dataview can be a one- to three-digit number for HIST or PROD status version-numbers, PROD for the current PROD-status version or Tnnn for test status versions.

Action:

Correct the version number used in the command.

IDSTSETC18 - VERSION must be 1 through 999 or T1 through T999

Reason:

The version number specified for DEQUEUE DATAVIEW must be a one- to three-digit number for Production or History status or Tnnn for Test status.

Action:

Correct the version number used in the command.

IDSTSETC67 - VERSION must be 1 through 999, PROD or ASIS

Reason:

The version number specified for ALL resources must be a number between 1 and 999, PROD, or ASIS.

Action:

Correct the version number used in the command.

IDSTSETC68 - VERSION must be 1 through 999, LAST, PROD or ASIS

Reason:

The version number specified for a program, panel, or report must be a number between 1 and 999, LAST, PROD, or ASIS.

Action:

Correct the version number used in the command.

IDSTSETC69 - SET IMPORT RESOURCE option specified is invalid

Reason:

The command SET IMPORT RES can accept as an operand only the option <entity-type> <version-clause> where <entity-type>=DVW, PGM, PNL, or RPT and <version-clause>=VER nnn, PROD, LAST, or ASIS.

Action:

Correct the errors and re-specify.

IDSTSETC70 - SET EXPORT PROGRAM option must be RESOURCE HISTORY YES or NO

Reason:

The correct form of the command is: SET EXPORT <PROGRAM> RESOURCES <DUPLICATE> HISTORY {YES|Y|NO|N}.

Action:

Correct the errors and re-specify.

IDSTSETC71 - SYSTEM short-system-id is not defined to Ideal

Reason:

You entered a SET command for a SYSTEM that was not defined in CA Ideal.

Action:

Check the spelling of the system name in the command or display all valid systems with the DISPLAY INDEX SYSTEM command.

IDSTSETC72 - USER short-user-id is not defined to Ideal

Reason:

The user name or ID specified in the command is not known to CA Ideal.

Action:

Check that the correct short-user-ID is specified and that it is spelled correctly.

IDSTSETC73 - EXIT NAME must be 1 to 8 character module name of exit

Reason:

The syntax of the command specifies two valid forms:

SET EXIT LIBRARIAN

SET EXIT NAME exit-name

The second form was apparently specified with an exit-name that exceeds 8 characters. A user-exit must be a valid non-CA Ideal program name.

Action:

Correct the errors and re-specify.

IDSTSETC74 - SET must be EXPORT, IMPORT, SOURCE, ERROR, TERMINAL, EXIT, OUT

Reason:

The word after the verb SET must be one of the keywords listed in the error message.

Action:

Correct the errors and re-specify.

IDSTSETC75 - SET EXIT must be NAME followed by exitname or LIBRARIAN

Reason:

The syntax of the command specifies two valid forms:

SET EXIT LIBRARIAN

SET EXIT NAME exit-name

SET EXIT was specified with an invalid form.

Action:

Correct the errors and re-specify.

IDSTSETC76 - SET SOURCE must be LISTING, DDNAME, BLKSIZE, DEVICE, TO SYSnnn

Reason:

(VSE only) SET SOURCE has the following valid forms:

SET SOURCE BLKSIZE blksize
SET SOURCE DDNAME file-name
SET SOURCE DEVICE device
SET SOURCE LISTING \{OFF|ON\}
SET SOURCE TO SYSnnn

You specified an invalid form of the command.

Action:

Correct the errors and re-specify.

IDSTSETC77 - IMPORT SYS must be a three-character system ID or ASIS

Reason:

The SET IMPORT SYSTEM command accepts the four-character value ASIS or a system-ID (up to three characters) as an operand. The SYSTEM entity-name cannot be used in this context.

Action:

Correct the errors and re-specify.

IDSTSETC78 - IMPORT VER must be 1 through 999 or ASIS

Reason:

The command SET IMPORT VERSION must specify either a numeric version number or the value ASIS. The command specified a version number that was not in the range of valid version numbers (001-999) and that was not the keyword ASIS.

Action:

Correct the errors and re-specify.

IDSTSETC79 - IMPORT USER must be a three-character user ID or ASIS

Reason:

The command SET IMPORT USER can accept as an operand either the keyword ASIS or a valid CA Ideal user-id (up to three characters). The command specified an invalid form of the operand.

Action:

Correct the errors and re-specify.

IDSTSETC80 - SOURCE LISTING only allows the option OFF

Reason:

The source listing produces a report of all entities on the external source file, regardless of whether specific entities were requested. The source listing option is ON by default, but can be disabled using the command SET SOURCE LISTING OFF. This is the only valid form of the command.

Action:

Correct the errors and re-specify.

IDSTSETC81 - SOURCE assignment must be TO SYS001 through SYS240

Reason:

The DOS assignment of the SOURCE listing output must be limited to valid DOS units SYS001-SYS240. You specified an invalid unit for the source listing output.

Action:

Correct the errors and re-specify.

IDSTSETC82 - SOURCE BLKSIZE must be numeric, from 80 to 32720

Reason:

The block size in DOS specified for the source listing output must be a multiple of 80 characters in the range 80 - 32720. Other values are invalid.

Action:

Correct the errors and re-specify.

IDSTSETC83 - SOURCE DEVICE must be DISK, SLTAPE or NLTAPE

Reason:

You specified an invalid DOS device-type for source listing output. Valid device types are DISK, SLTAPE, NLTAPE.

Action:

Correct the errors and re-specify.

IDSTSETC84 - SOURCE DDNAME must be 1 to 8 character ddname or filename

Reason:

The operand of the SET SOURCE DDNAME command must be a valid eight-character OS DDNAME as defined by IBM OS Job Control Language. The DDNAME specified was incorrectly named.

Action:

Correct the errors and re-specify.

IDSTSETC86 - IMPORT DUPLICATE must be REPLACE, NEXT VER, SKIP or QUIT

Reason:

The SET IMPORT DUPLICATE command can take only one of the following operands: REPLACE, NEXT VERSION, SKIP, or QUIT. See documentations for details of these options. You specified an invalid option as an operand of SET IMPORT DUPLICATE.

Action:

Correct the errors and re-specify.

IDSTSETC87 - IMPORT NEW SYS must be a three-character system ID or ASIS

Reason:

The SET IMPORT NEW SYSTEM command accepts the four-character value ASIS or a system-ID (up to three characters) as an operand. The SYSTEM entity-name cannot be used in this context.

Action:

Correct the errors and re-specify.

IDSTSETC88 - IMPORT NEW VER must be 1 through 999, NEXT or ASIS

Reason:

The command SET IMPORT NEW VERSION must specify either a numeric version number, the keyword NEXT, or the value ASIS. The command specified version number that was not in the range of valid version numbers (001-999) and that was not one of the designated keywords. See documentation for details of these options.

Action:

Correct the errors and re-specify.

IDSTSETC89 - IMPORT NEW USER must be a three-character user ID or ASIS

Reason:

The command SET IMPORT NEW USER can accept as an operand either the keyword ASIS or a valid CA Ideal user-id (up to three characters). The command specified an invalid form of the operand.

Action:

Correct the errors and re-specify.

IDSTSETC90 - VERSION number must be between 1 and 999

Reason:

You specified a version number, but it was not in the valid range 001-999.

Action:

Correct the errors and re-specify.

IDSTSETC91 - EXPORT SYS must be a three-character system ID

Reason:

The command SET EXPORT SYSTEM accepts only the short-system-id as an operand. The SYSTEM entity-name is not acceptable in this context.

Action:

Correct the errors and re-specify.

IDSTSETC92 - EXPORT VERSION must be 1 through 999, PROD or LAST

Reason:

The command SET EXPORT VERSION can take as an operand the keywords PROD or LAST; or it can take a numeric version-number in the valid range 001-999. You specified an invalid operand.

Action:

Correct the errors and re-specify.

IDSTSETC93 - EXPORT USER must be a three-character user ID

Reason:

The command SET EXPORT USER can accept as an operand only a valid CA Ideal user-id (up to three characters). The command specified an invalid form of the operand. The user entity-name is invalid in this context.

Action:

Correct the errors and re-specify.

IDSTSETC94 - SET SOURCE must be LISTING or DDNAME

Reason:

(Non-VSE only) The command keywords SET SOURCE must be followed by one or the other of the keywords DDNAME or LISTING. The word in the command encountered was not one of these keywords. The valid forms of the command are:

SET SOURCE DDNAME ddname

SET SOURCE LISTING OFF

There are no other valid forms of this command.

Action:

Correct the errors and re-specify.

IDSTSETC95 - SET TERMINAL only allows the option 5550

Reason:

This option is provided to support DBCS data.

Action:

Correct the errors and re-specify.

IDSTSETC96 - SET ERROR must be CONTINUE or QUIT

Reason:

You specified an invalid option with the SET ERROR command. See documentation for details.

Action:

Correct the errors and re-specify.

IDSTSETC97 - SET IMP must be SYS, VER, USR, NEW SYS, NEW VER, NEW USR or DUP

Reason:

You specified an invalid option for the SET IMPORT command. The valid options are properly abbreviated in the error message. See documentation for details.

Action:

Correct the errors and re-specify.

IDSTSETC98 - SET EXPORT must be SYSTEM, VERSION, USER or PROGRAM.

Reason:

You specified an invalid option for the SET EXPORT command.

Action:

Correct the errors and re-specify.

IDSTSETC99 - @I$DIALMASK must be ALL or /string/

Reason:

The syntax of SET @I$DIALMASK provides two valid forms:

SET @I$DIALMASK ALL
SET @I$DIALMASK 'string'

Neither of these forms was used.

Action:

Correct the errors and re-specify.

IDSTSETP01 - IDSTSETP06

IDSTSETP01 - Option not recognized

Reason:

The specified option in the SET command is invalid.

Action:

Ensure that the option specified for the SET command is valid and is spelled correctly.

IDSTSETP02 - Insufficient authorization for this command

Reason:

The user does not have sufficient authorization to use this command.

Action:

Ask a CA Ideal Administrator to execute the command.

IDSTSETP03 - INTERR: Internal command format cannot be recognized

Reason:

An unexpected or unusual condition terminated a CA Ideal command or run-time application.

Action:

Contact CA Ideal Technical Support. Obtain information as illustrated in the CA Ideal Problem Determination Guide to facilitate your call.

IDSTSETP06 - Source file BLKSIZE must be a multiple of 80

Reason:

The message is self-explanatory.

Action:

Repeat this command with the proper choice of number.

IDSTTABP01

IDSTTABP01 - No valid EXPORT, IMPORT or PRODUCE commands specified

Reason:

The Source Transport utility took no action.

Action:

Correct the errors and re-specify.