Power2000 & Cobol

[Deskin, Bob]

The COBOL Language Sensitivity in Power2000 version 1.1 is documented in
the online help. It's an unsupported feature. We never hid the fact that
it was there, but we didn't shout it from the rooftops either. Two
reasons - besides that it was unsupported. First, it's based on OpenVMS
COBOL (lucky for you) and COBOLs are not the same. So there are some HP
COBOLisms not supported. Check the online help under Unsupported
Features and Utilities. The other reason is that there is no COBOL
Knowledge Base. We feel that a large part of the value of the product is
the Knowledge Base. Of course there's no reason why someone couldn't
produce a COBOL Knowledge Base. The big problem with COBOL is locating
those date items to begin with. As for the indicator column, all COBOLs
use one, the question is where does it go. There must be a column in
which to specify comments or hyphens (for continuation).

Bob Deskin              
Senior Product Advisor  bob.deskin@cognos.com
Cognos Inc.             (613) 738-1338 ext 4205 FAX: (613) 228-3149
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA


> ----------
> From: 	Stewart, Mark[SMTP:MStewart@VICTORIA.COM]
> Sent: 	June 19, 1998 2:49 PM
> To: 	powerh-l@lists.swau.edu
> Subject: 	Power2000 & Cobol
> 
> 
> Mr. Blackadder one of the developers of Power2000 at Cognos informed
> me  at
> the conference that Power2000 Ver 1.1 has the smarts to scan COBOL for
> Y2K
> issues based on the issues companies in the U.K. had indentified.  Our
> COBOL
> developers here have a mission critical Payroll application written in
> 100%
> COBOL.  I have discussed the possibility of using Power2000 against
> this
> system with one of those developers.  Her eyebrows went up when I
> informed
> her that Power2000 has COBOL smarts built in.  She had used the
> product on a
> much smaller scale before by turning off the knowledge base and adding
> her
> own issues.  In the unsupported help section under COBOL is says the
> following:
> 
> In order to properly scan COBOL files, you must add an entry into the
> Power2000 Project configuration file (file extension P2P) to indicate
> which
> column is to be used as the Indicator Column.  The column is usaully 1
> or 7.
> 
> As far as I know this indicator column is only indicative of COBOL
> applications found on an IBM machines.  Cobol applications on DEC
> machines
> (in this case an ALPHA) do not use Indicator Columns.  
> 
> Does this line still have to be added to the .P2P file when OpenVMS is
> the
> operating system?  If anything, what exactly should I add to the .P2P
> file
> when scanning COBOL code in OpenVMS?
> 
> Also I have informed them that Power2000's sensativity is only applied
> to
> .COB programs and not to .SCO (SQL embedded Cobol programs) and so we
> will
> make a list of all .SCO and rename them back after we put them back on
> the
> Alpha.
> 
> 
> Mark Stewart
> Consultant
> OpenVMS Alpha V7.1-1H1
> Oracle Rdb    V7.0-1
> PH 4GL        7.10.F4
> 
> 
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> = = =
> Subscribe: "subscribe powerh-l" in message body to
> majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to
> majordomo@lists.swau.edu
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> This list is closed, thus to post to the list, you must be a
> subscriber.
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.