Skip to main content

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

Wow, you are correct. The Graphical Working Storage editor will not allow an underscore. I see no way of changing that behavior at this time (Tools/ Options). I will report this to Development. This appears to be a limitation of that editor.

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

You could leave the "-" in the COBOL program variable names and use a stylesheet during import or export to change the name spelling to replace the "-" with "_" in the XML document.

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

I'll provide one other option. Create a text file copybook with the variables, using underscores. Now in the AcuBench / Tools / Options / Code Generator/ Program tag, there is an area where you can have AcuBench add in your own copybooks into the Generated Code. This would provide a workaround of not needing to use the Graphical Working Storage designer.

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

Is this is a SOAP service using the XSLT files provided with BIS? i.e. Cobol_to_Soap.xsl, Cobol_to_WSDL.xsl, and Soap_to_COBOL.xsl? If so, these XSLT files have a provision for a so-called "spelling dictionary" which you can use to map COBOL names to your own user-defined names. This has worked well for me, where I map COBOL names with hyphens to CamelCase names which appear in the WSDL and SOAP messages.

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

Odd to see this. With an xfd the cobol IP-VS-MESSAGE variable is seen as IP_VS_MESSAGE by windows. They are identical.

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

XFDs are used in many cases with Databases, and many databases support the _ but not dashes in column names

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

With ODBC, the XFD, and Acu4gl, the fd with hypens is seen as underscore by the system. That's why in SQL Server tables, Oracle tables etc, we use the underscore instead of the hyphen but the cobol sees it as a hyphen via the FD. The same cobol gui programs use vision, sql server, Oracle, etc using Acu4GL and the xfd's. The MS OS sees underscores even when it is looking at the vision files via XFD's and ACUXDBC.

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

With ODBC, the XFD, and Acu4gl, the fd with hypens is seen as underscore by the system. That's why in SQL Server tables, Oracle tables etc, we use the underscore instead of the hyphen but the cobol sees it as a hyphen via the FD. The same cobol gui programs use vision, sql server, Oracle, etc using Acu4GL and the xfd's. The MS OS sees underscores even when it is looking at the vision files via XFD's and ACUXDBC.

I am creating a gateway program to be used in XBIS that will drive a new process we are developing.  Our .net team requested that I update all '-' in variable names to "_".  As I attempted to do this in AcuBench the Working Storage screen would not accept "_" and would automatically convert them back to a "-".  Does anyone know why this is happening?  An Example variable name is: 'IP-VS-Message'...I had hoped to make that 'IP_VS_Message'.  The only option that I could use was to remove the '-' completely.  This made the final variable name: 'IPVSMessage' which it took but is a bit confusing.

 

Thanks

FYI; Acubench works on linux via Facetwin. Try it out sometime. Also, comment out the Acubench auto-generated event logic and point it to exception logic. Your documentation admits exception logic is more reliable than the event logic and it truly is.