ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Incomple Message Set during deploy

Post new topic  Reply to topic
 Incomple Message Set during deploy « View previous topic :: View next topic » 
Author Message
CHERIANV
PostPosted: Mon Aug 15, 2005 10:49 am    Post subject: Incomple Message Set during deploy Reply with quote

Apprentice

Joined: 15 Feb 2002
Posts: 43
Location: New York

Hi,
I have been having problems in deploying the following message set to a Z/OS Broker . The import of the COBOL structure works fine excepting for the following warnings :

Summary:
No. of Errors: 0
No. of invalid COBOL errors: 0
No. of unsupported COBOL warnings: 0
No. of Types created: 7
No. of Elements created: 129
No. of Values created: 114

Warning: The following Types are incomplete:
JBGAD0S_STRUCT_TYPE
GARS_EOSE_ORDERS_LEGACY_STRUCT_TYPE

Warning: The following Elements are incomplete:
JBGAD0S_STRUCT
ADDRESS
Import was successfully completed

But when I attempt to create a message using the compound type GARS_EOSE_ORDERS_LEGACY_STRUCT_TYPE and deploy this message set to the Broker , it fails with the following error . Any input is appreciated as I have been trying to scrutinize the COBOL structure and am not sure what is wrong.

ERROR DURING DEPLOY
BIP1934E: Message Set (EOSE_GARS_LEGACY_ORDERS, Level 1) is incomplete.

A Runtime Dictionary or Custom Wire Format extract cannot be run on incomplete message set (EOSE_GARS_LEGACY_ORDERS, Level 1). The probable cause for this is one or more incomplete messages. For example: A message containing an element of an empty compound type.

Update any incomplete resources that belong to the message set and then retry the operation.



COBOL Structure :

01 GARS_EOSE_ORDERS_LEGACY_STRUCT.
03 JBBXRTS_STRUCT.
05 IDBSRE0 PIC X(10).
05 SJBABTX PIC X(10).
05 DAYTIME PIC X(26).
05 COPUMCO PIC X(3).
05 IUSRTPU PIC X(.
05 ROOTNAME PIC X(.
05 ISYSIDY PIC X(4).
05 ISYSRML PIC X(3).
05 CPGMRSC PIC X(1).
05 ITRNBUS PIC X(.
03 JBGSD0S_STRUCT.
05 IDBSRE01 PIC X(10).
05 FILLER PIC X(4).
05 SUPPLY_CAT PIC X(1).
05 OCL_CODE PIC X(2).
05 PLANT_OF_CONTROL PIC X(12).
05 CUST_NUMB_OWNER PIC X(.
05 CUST_NUMB_USER PIC X(.
05 MARKETING_RESP PIC X(2).
05 SYSTEM_NUMBER PIC X(7).
05 SYSTEM_TYPE PIC X(4).
05 PLANT_INT_ID PIC X(12).
05 SCHED_ENTITY_NUM PIC X(7).
05 REMOVAL_ENTITY_NUM PIC X(5).
05 METHOD_OF_TRANSPRT PIC X(4).
05 CURRENT_SCHED_DATE PIC X(10).
05 CSD_STATUS PIC X(1).
05 ROUTING_CODE PIC X(1).
05 SHIP_TO_OU PIC X(12).
05 EMERG_ORD_ENT_IND PIC X(1).
05 ROUTING_PLANT PIC X(12).
05 FILLER2 PIC X(12).
03 JBGOD0S_STRUCT.
05 IDBSRE02 PIC X(10).
05 FILLER3 PIC X(2).
05 RESCHEDULE_NUM PIC S9(09) USAGE COMP-4.
05 DOCUMENTS_QTY PIC S9(09) USAGE COMP-4.
05 PLANT_ALT_NUM PIC S9(04) USAGE COMP-4.
05 SUPPLY_ORDER_REF PIC X(12).
05 TRANSACTION_TYPE PIC X(2).
05 REASN_FOR_SUPP_ORD PIC X(1).
05 SOURCING_OU PIC X(12).
05 CANCEL_REASON PIC X(2).
05 CONF_REQD_FLAG PIC X(1).
05 ORDER_ENTRY_DATE PIC X(10).
05 SUPPLIER_ANALS_DTE PIC X(10).
05 SUPPLIER_INIT_DTE PIC X(10).
05 PLAN_TRANSFER_DTE PIC X(10).
05 PLAN_SHIP_DTE PIC X(10).
05 PLAN_ARR_CNTRY_DTE PIC X(10).
05 DELIV_INIT_DUE_DTE PIC X(10).
05 PLAN_DISTR_DTE PIC X(10).
05 CRAD PIC X(10).
05 ORDER_DESIG_DATE PIC X(10).
05 ORGANISATION_CODE PIC X(1).
05 LIQUIDATED_DAMAGES PIC X(1).
05 MAT_PAT_IND PIC X(1).
05 PRIORITY_CODE PIC X(1).
05 CUSTOMER_SET_UP PIC X(1).
05 GROUP_CODE PIC X(2).
05 SHIP_INSTRUCT_CODE PIC X(1).
05 FILLER5 PIC X(5).
05 BASE_MC_SERIAL_NO PIC X(9).
05 LINKED_MES_ORN PIC X(12).
05 MES_ORDER_CLASS PIC X(1).
05 REQUESTED_SAC PIC X(1).
05 PLAN_PM_SHIP_DTE PIC X(10).
05 CE_BRANCH_OFF PIC X(3).
05 SELLING_BRANCH_OFF PIC X(3).
05 INSTALL_BRANCH_OFF PIC X(3).
05 DLV_BRANCH_OFFICE PIC X(3).
05 ORDER_RES_IND PIC X(1).
05 ORDER_ALT_IND PIC X(1).
05 PLANT_ORIGIN_CODE PIC X(2).
05 FILLER6 PIC X(1).
05 MES_FLAG PIC X(1).
05 REQ_SHIP_DATE PIC X(10).
05 TYPE_OF_AGREEMENT PIC X(1).
05 SER_IND PIC X(1).
05 POWER_CODE PIC X(1).
05 MANUFACT_MODEL PIC X(3).
05 METHOD_OF_SCHED PIC X(1).
05 PROD_SUPPLY_GRP PIC X(5).
05 ANALYSIS_CODE PIC X(2).
05 QUANTITY PIC S9(09) USAGE COMP-4.
05 NPM_INDICATOR PIC X(1).
05 PHYSICAL_SHIPMENT_IND PIC X(1).
05 ORDER_LINE_TYPE PIC X(1).
05 ID_BPT PIC X(4).
05 ORD_SYSTEM_ID PIC X(4).
05 TYPE_OF_BUSINESS PIC X(1).
05 POINTS PIC S9(09) USAGE COMP-4.
05 FIRM_ORDER_FLAG PIC X(1).
05 FILLER7 PIC X(39).
03 JBGRD0S_CNT PIC S9(09) USAGE COMP-4.
03 JBGRD0S_STRUCT OCCURS 0 TO 9999 TIMES
DEPENDING ON JBGRD0S_CNT.
05 IDBSRE03 PIC X(10).
05 SUPPLY_ORDER_REF1 PIC X(12).
05 TRANSACTION_TYPE1 PIC X(2).
05 TYPE_OF_REMARKS PIC X(1).
05 REMARKS PIC X(60).
03 JBGAD0S_STRUCT.
05 IDBSRE04 PIC X(10).
05 ADDRESS PIC X(180).
05 CUST_NUMB_ADDRESS PIC X(0.
05 ADDRESS_NUMBER PIC X(05).
05 PHONE_NUMBER PIC X(16).
05 POST_CODE PIC X(30).
05 LANGUAGE_CODE PIC X(01).
05 CUSTOMER_REF PIC X(40).
05 FILLER8 PIC X(120).
03 JBGDD0S_CNT PIC S9(09) USAGE COMP-4.
03 JBGDD0S_STRUCT OCCURS 0 TO 9999 TIMES
DEPENDING ON JBGDD0S_CNT.
05 IDBSRE05 PIC X(10).
05 DLV_INSTRUCT PIC X(60).
05 FILLER9 PIC X(10).
03 JBGLD0S_CNT PIC S9(09) USAGE COMP-4.
03 JBGLD0S_STRUCT OCCURS 0 TO 9999 TIMES
DEPENDING ON JBGLD0S_CNT.
05 IDBSRE06 PIC X(10).
05 FILLER10 PIC X(2).
05 PRD_TYPE_QTY_REQD PIC S9(09) USAGE COMP-4.
05 SUPPLY_ORDER_REF2 PIC X(12).
05 TRANSACTION_TYPE2 PIC X(2).
05 PT_BUS_ID PIC X(25).
05 TYPE_OF_PROD_TYPE PIC X(3).
05 ID_SAC PIC X(5).
05 NPM_LINK_CODE PIC X(1).
05 REVENUE_CODE PIC X(1).
05 FILLER11 PIC X(20).

Thanks,
Cherian
Back to top
View user's profile Send private message
EddieA
PostPosted: Mon Aug 15, 2005 11:47 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Quote:
and deploy this message set to the Broker , it fails with the following error

And what did you expect if you haven't correct the errors from the Import.

I'd suggest changing the field "ADDRESS" into another name and re-Import. It looks like that's what's causing the problem.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
CHERIANV
PostPosted: Mon Aug 15, 2005 1:23 pm    Post subject: Reply with quote

Apprentice

Joined: 15 Feb 2002
Posts: 43
Location: New York

Hi,
Thanks for pointing the field "ADDRESS". It was a complete oversight on my thinking the problem to be something around COBOL. The deploy worked fine now.

Cheers!
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Incomple Message Set during deploy
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.