CA Fast Load Vs BMC Load Plus

Well, I've been compiling this for a while now. Here is a list of CA/Platinum's Fast Load utility keywords and the equivalent BMC's Load Plus keywords.


If you have any questions, or something doesn't make sense, or if you are looking for something else, please let me know (comments/email/chat).


I'm sorry, I couldn't find a way to insert a Word Document (with a table) into this blog, so I pasted the table here as an image.


Thanks !!

Fast Load abend - IEC146I 513-04

You are running Platinum Fast Load job and the job fails on you with an "IEC146I 513-04" error.

IEC146I 513-04 means
"An OPEN macro instruction was issued for a magnetic tape data set allocated to a device that already has an open data set on it. Make sure that the first data set is closed before the second is opened, or allocate the second data set to a different device. This error may be due to a
previous abnormal end associated with the same unit in the same step. If so, correct the error causing the previous abnormal end."

Problem:
As per the above message, you are trying open the dataset for two different purposes in the same job step.

In your LOAD card, see what you've specified for INDDN. In my case, I had specified INDDN SYSREC.

Fast Load user guide says "If you will be performing an OUTPUT-CONTROL ALL type load, and you want to specify INDDN SYSREC, you must also specify UNLDDN and change its default value. Otherwise, Unicenter Fast Load will try to use SYSREC as an input and a work file."

OUTPUT-CONTROL ALL is the default. I noticed that I didn't have a UNLDDN DD name in my JCL.

Fix:
Either specify a UNLDDN DD in your JCL step or change INDDN to something other than SYSREC. I changed it to SYSULD and it worked.

Platinum Fast Load Error "PFL8013E"

If a Fast Load job fails with PFL8013E (Error Description: A table within Table Space that has multiple versioned rows is not supported for this release of Unicenter Fastload. Reason: This DB2 V8 feature is not yet supported by Unicenter Fast Load. Processing terminates), it could be because the tablespace is in AREO (Advisory Reorg pending) status. This happens in a DB2 V8 NFM subsystem, with Fast Load (version r11.5) Resume NO REPLACE option specified.

How will you fix this? There are a few options that you can try:

1. Run REORG utility on the tablespace and retry loading.

2. If that doesn't work, drop and recreate the table and then load the table using Fast Load

3. If that doesn't work, try IBM LOAD. That should definitely work.