Skip to main content

Error while creating Alternate index in Enterprise Server

  • October 30, 2020
  • 8 replies
  • 2 views

Hi, 

Can someone help me understand what do the below errors correspond to. Did not find anything related to status code in the manuals.

I was trying to create an alternate index for a VSAM file.   

JCLAM0177S(12) - Unexpected return-code 22 from CALLRB.

JCLAM0178S(12) - Unexpected status-code 22 from CALLRB.

 

Thanks.

 


#EnterpriseServer

8 replies

  • Author
  • Rocketeer
  • 19312 replies
  • October 30, 2020

Hi, 

Can someone help me understand what do the below errors correspond to. Did not find anything related to status code in the manuals.

I was trying to create an alternate index for a VSAM file.   

JCLAM0177S(12) - Unexpected return-code 22 from CALLRB.

JCLAM0178S(12) - Unexpected status-code 22 from CALLRB.

 

Thanks.

 


#EnterpriseServer
A status 22 may indicate a dupe key on the alternate index, is it defined to allow duplicates. That may resolve the 22, but the next question would be should there be dupicates?

  • Author
  • Rocketeer
  • 19312 replies
  • October 30, 2020
A status 22 may indicate a dupe key on the alternate index, is it defined to allow duplicates. That may resolve the 22, but the next question would be should there be dupicates?

It was not supposed to have duplicates but it did and the alternate index was being defined with UNIQUEKEY. 

Thanks Steve.

One more thing, when a job step fails with this error, all the following job steps to create the alternate indexes for other files fail too with the same error even when there are no duplicates. I have to then restart the server to submit the following jobs steps, which now run successfully without any issue. Is there a way to avoid this server restart? 

 

 

 

 


  • Author
  • Rocketeer
  • 19312 replies
  • October 30, 2020

It was not supposed to have duplicates but it did and the alternate index was being defined with UNIQUEKEY. 

Thanks Steve.

One more thing, when a job step fails with this error, all the following job steps to create the alternate indexes for other files fail too with the same error even when there are no duplicates. I have to then restart the server to submit the following jobs steps, which now run successfully without any issue. Is there a way to avoid this server restart? 

 

 

 

 

Sounds odd. What version of the product, whet environment windows/Linux. The steps actually execute, different file and different file name and it fails anyway?



How are you building the Alternate indicies?



  • Author
  • Rocketeer
  • 19312 replies
  • October 31, 2020
Sounds odd. What version of the product, whet environment windows/Linux. The steps actually execute, different file and different file name and it fails anyway?



How are you building the Alternate indicies?


Enterprise Developer Unix Components 2.2 - Update 1

Yes different files and filenames, when I say fail here, I mean COND code 12.

For eg: step 1: Tries to create an alternate index for a file and it fails coz the alternate index had dups.

               step 2: Tries to create an alternate index for a different file, the alternate index  has no dups, but the                                      step still fails.

So now, I restart the server, I execute step 2, it creates the alt index without any issues.

Using IDCAMS(or MFJAMS here) to create alternate index, if this is what you are asking.


  • Author
  • Rocketeer
  • 19312 replies
  • November 2, 2020

Enterprise Developer Unix Components 2.2 - Update 1

Yes different files and filenames, when I say fail here, I mean COND code 12.

For eg: step 1: Tries to create an alternate index for a file and it fails coz the alternate index had dups.

               step 2: Tries to create an alternate index for a different file, the alternate index  has no dups, but the                                      step still fails.

So now, I restart the server, I execute step 2, it creates the alt index without any issues.

Using IDCAMS(or MFJAMS here) to create alternate index, if this is what you are asking.

That's quite an old product, one that went off support back in 2018. It does sound like a possible bug, but because it's off support help will be somewhat limited. There is a hotfix available on the support website for 2.2 Update1 that might fix it, there is also an Update two which will contain more updates and fixes to know bugs which again may help.



It the JCL are you doing a BDLINDEX, or are you doing a delete and define of the dataset and indices followed by a repro in? That second option, if you are not already doing it may help.



  • Author
  • Rocketeer
  • 19312 replies
  • November 3, 2020
That's quite an old product, one that went off support back in 2018. It does sound like a possible bug, but because it's off support help will be somewhat limited. There is a hotfix available on the support website for 2.2 Update1 that might fix it, there is also an Update two which will contain more updates and fixes to know bugs which again may help.



It the JCL are you doing a BDLINDEX, or are you doing a delete and define of the dataset and indices followed by a repro in? That second option, if you are not already doing it may help.


I am delete/defining the VSAM base cluster for multiple files in one job(different steps) and then doing repro in a separate job before proceeding to delete/define the Alternate Indices in the third job. I am doing BLDINDEX, however it gets ignored by ES. 

I will surely look into the product updates. Hopefully that will help. 

Thanks.

 

 


  • Author
  • Rocketeer
  • 19312 replies
  • November 3, 2020

I am delete/defining the VSAM base cluster for multiple files in one job(different steps) and then doing repro in a separate job before proceeding to delete/define the Alternate Indices in the third job. I am doing BLDINDEX, however it gets ignored by ES. 

I will surely look into the product updates. Hopefully that will help. 

Thanks.

 

 

If you do the delete and define off the base cluster and alternate index, then the repro and the alternate index's should get populated properly.

Good luck

  • Author
  • Rocketeer
  • 19312 replies
  • November 5, 2020
If you do the delete and define off the base cluster and alternate index, then the repro and the alternate index's should get populated properly.

Good luck

It does get populated correctly, however the ES required a restart every time the duplicate error was encountered while creating the Alternate index. I fixed the bad data and it is working fine now.

Thanks for your help Steve.