Re: testing an SQL procedure -- MIDRANGE-L

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

Subject: Re: testing an SQL procedure
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Tue, 02 Sep 2014 15:06:29 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 9/2/2014 2:45 PM, Gary Thompson wrote:

Thanks Rob, Thanks Buck,
I ran that select on prod and test parts and both return *FILE not found
tried FROM group_ptf_info and FROM wrkptfgrp ?

WRKPTFGRP is a command, not the name of a table. Rob made a good point
that WRKPTFGRP is actually quite old. select * from group_ptf_info
works on my 7.2 system.

I'll suggest those two links to ops mgr
Also, my user prof has all except *SECADM

Try WRKPTFGRP on a command line.
--buck

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: testing an SQL procedure , Gary Thompson

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.