Anyone Have Experience with API for Retrieve Device Description QDCRDEVD) -- 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: Anyone Have Experience with API for Retrieve Device Description QDCRDEVD)
From: Chuck Lewis <clewis@xxxxxxxxxx>
Date: Fri, 09 Nov 2001 11:50:43 -0500
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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi Folks,

Newbie to API's and I was trying to figure out how to use the API that
retrieves device descriptions to replace a fairly complicated code I
have (that I had to redo when we went from V4R1 to V4R5 this past
weekend...) to do this. Looks like it might be much easier and less
"change prone" than what I am currently doing (copy the spool file
generated from the DSPDEVD command to a file).

Thanks !

Chuck

As an Amazon Associate we earn from qualifying purchases.

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.