× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Mike

Yeah, my idea was to get a starting point - you'd have to parse out the intricate details.

There's an option to include PCML or something when compiling - I wonder if that'd give you something useful.

Vern

On 5/12/2015 12:27 PM, Michael Wisolmerski wrote:
Vernon -

Thanks, but I was thinking more of something I could exchange with non-IBM
system developers. I appreciate the response.


*Thanks -*

*Mike W.*


*Michael Wisolmerski*
AOPS | Office Depot, Inc.
6600 Military Trail | Boca Raton, FL  33496
Tel: 561.438.1332 | Michael.Wisolmerski@xxxxxxxxxxxxxxx

[image: Office Depot | Max]

message: 6
date: Mon, 11 May 2015 14:16:29 -0500
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Extract Outline Information

A compile listing with *NOGEN will give you all the right size information.

On 5/11/2015 12:35 PM, Michael Wisolmerski wrote:
Hi -

Does anyone know of a way to extract the Outline information?
Specifically,
we use large DSs with many fields to communicate with other systems and it
would be nice to be able to get an size correct list that we could send
other developers. We use a lot of LIKE definitions so it's quite a bit of
work to get correct DS sizing.


*Thanks -*

*Mike W.*


*Michael Wisolmerski*
AOPS | Office Depot, Inc.
6600 Military Trail | Boca Raton, FL  33496
Tel: 561.438.1332 | Michael.Wisolmerski@xxxxxxxxxxxxxxx


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.