Author Topic: OS390 under version 9.5  (Read 2167 times)

DDP021

  • Sr. Member
  • ****
  • Posts: 343
    • View Profile
OS390 under version 9.5
« on: June 01, 2017, 03:08:01 AM »
We are attempting to upgrade to 9.5.  we have numerous applications defined with -V## at the end.  The V## number changed when there was something updated on the application.  In current production (8.5) when we run the ingestion jobs, we just need to input the application name and not include the -V##.  Somewhere it knows to use the latest application version.  Assuming its in some table?? But in testing ingestion of mainframe files using OS/390, the JCL we run for testing requires us to input the Application with the -V##.  Below is a screen shot of part of the JCL.  As you can see, the RPT12 indicated DLRACCT-V11.  This is the latest Application id.  If the -V11 isn't included, ingestion fails not finding the application id.  In current production, we aren't required to include the -V11.  It knows to go to the latest version.  Does anyone know where this information is stored on the server and what is needed on the JCL to automatically use the latest application version?

STEP1 EXEC PODA30SU,RPTID=DLRACCNT,       
      RPTDSN=XAUT01.ODA.DLRACCNT,         
      RPTI2='DLRACCNT-V11',               
      AG='PDOC06009'                       

DDP021

  • Sr. Member
  • ****
  • Posts: 343
    • View Profile
Re: OS390 under version 9.5
« Reply #1 on: June 01, 2017, 07:47:11 AM »
Just and update...Apparently when we first converted to CMOD, IBM created a ODSCRT table...This table is used currently in production (8.5) but apparently something is different with 9.5 as this is no longer being referenced when attempting to ingest...Just as an example of what is happening...

Say we have an application called ABC123.  In the old OnDemand system, if a change was made, the application name change..So we could have multiple names, (ie ABC123-v01, ABC123-v02, etc).  When we had the conversion, we had to migrate all versions.  But when the JCL ran to pull in the data into CMOD, the ODSCRT table was referenced to write to the most recent application version.  All we had to reference in the JCL for the application was ABC123.  What is happening with 9.5 is this table isn't being used.  If we want to load anything under 9.5, we need to include the entire application name (ie ABC123-V02)....We have to use the OS390 indexer due to the data...These being old mainframe files that weren't formatted consistently...Indexing using ACIF would fail....Just curious of anyone knows what needs to be done in order for 9.5 to recognize this ODSCRT table?

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1200
    • View Profile
Re: OS390 under version 9.5
« Reply #2 on: June 01, 2017, 11:39:00 AM »
D -

Anything that starts with ARS comes from CMOD development.

Anything that starts with ODS comes from IBM's CMOD Services team.

You're probably going to have to contact the CMOD Services folks.

Ed

#zOS #ODF