How to tell if a GEN model has been re-converted to use RESTful API
search cancel

How to tell if a GEN model has been re-converted to use RESTful API

book

Article ID: 267930

calendar_today

Updated On:

Products

Gen

Issue/Introduction

 
SQL to confirm if models were re-converted after the schema reload (CEJOB05) for LU03408 PTF was run. 
 
 

 

Environment

Release : 8.6

Resolution

With LU03408, Model Conversion was modified to add a new system object that is needed in order to add 'Call REST' statements to existing models.  Otherwise, the toolset will display a message saying you must convert your model first.

The new system object created has the object type of XSIFTYPE and the name of "RESTM-1.1" which is associated with the existing system object XSAPPENV.

You can use WALKENCY to verify the new XSIFTYPE was created or run the SQL that follows below.

To use WALKENCY:

1. Enter model name and object type of XSIFTYPE 

2. Verify there is an XSIFTYPE with the Name of “RESTM_1.1

 To run SQL, replace your sqlid and your modelname:

 SET CURRENT SQLID='your sqlid';                                    

--                                                              

-- SELECT XSIFTYPE (OTC 599) WITH NAME (PTC 224) =  'RESTM_1.1'

--                                                             

SELECT OBJ_ID AS "XSIFTYPE OID", PROP_CHAR_VAL AS "NAME"       

  FROM DOBJ, DPRP, DMDL                                        

 WHERE MODEL_NAME='your model name'                       

   AND OBJ_MODEL_ID=MODEL_ID                                   

   AND OBJ_TYPE_CODE =599                                     

   AND OBJ_ID =PROP_OBJ_ID                                    

   AND PROP_TYPE_CODE= 224                                    

   AND PROP_CHAR_VAL ='RESTM_1.1';     

Additional Information

Focus is on the hold action for patch LU03408 to "Reload the Schema tables", for the Host Encyclopedia, "using CEJOB05 (or CAJOB05) job". 

Reconvert any models that may have 'Call REST' statements added to the models at some point in the future. 

Migration has been modified to first Adopt the new System Objects used for 'Call External' and 'Call REST' statements to prevent duplicate System Objects from being created by a Migration. It is not required to perform an Adoption on all models in the family at this time. However, if you would prefer not to wait until a Migration, you could go ahead and Adopt the System Objects now.

The change that was made in the LU03408 PTF was to the Schema Association Table (SASC). The aggregate action value (stored in the AT_AGG_ACT column) was changed from an 'I' (Include) to a 'C' (Copy) for one row representing the association XSIFACE MANAGDBY XSIFPROJ. This change is needed for the migration of 'Call REST' statements. The LU03408 PTF delivers an updated version of the LASC92A6, which is in the CEHBDATV dataset.  It is a one-character change which prevents a problem that could occur during Migration. If you compare the old LASC92A6 member to the one delivered with the PTF, you will see XSIFACE XSIFPROJCR instead of XSIFACE XSIFPROJIR. In the case of this PTF, we need customers to run the CEJOB05 job again to reload the Schema tables with the updated content.