× 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.



On 11/26/2013 3:19 PM, rob@xxxxxxxxx wrote:
Are you a speed reader that skips stuff

More often that I like :)

When I edited the cobol source it syntax checked it. Yet I do not
have the cobol compiler.

I'm guessing the syntax rules for COBOL are shipped with SEU automatically. PL/1 probably adds a hook into the syntax checker when it's installed.

What happens if you change the member type to CLLE and pull that up
with STRSEU?

If I change the member type to TXT it saves without a problem.

Or, did using RDP fix any possible errant characters?

No, it still crashed even after editing with RDP. Of course RDP doesn't use host based syntax rules and (more importantly) doesn't know anything about PL/1.

But, since you are on a supported version of the OS now you should
be able to call IBM.

If we continue to have the problem after installing the correct version of PL/1, I will.

The issue is moot until we do get a working version of PL/1 ... editing the source member doesn't help much if we can't compile the code when we promote.

Did I miss the results of the WRKPTFGRP I asked for?

No. I didn't think it was relevant. I'm 90% sure the problem is related to our PL/1 compiler.

I just checked something and, when I start SEU, library QPLI is in the PRD portion of the the library list.

david



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.