Re: QSPDSPFM parameters -- MI400

× 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: [MI400] QSPDSPFM parameters
From: Bobby Hicks <Robert.Hicks@xxxxxxxxxxxxxxxx>
Date: Thu, 18 Mar 2004 13:06:24 -0500
List-archive: <http://archive.midrange.com/mi400>
List-help: <mailto:mi400-request@midrange.com?subject=help>
List-id: MI Programming on the AS400 / iSeries <mi400.midrange.com>
List-post: <mailto:mi400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/mi400>, <mailto:mi400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/mi400>, <mailto:mi400-request@midrange.com?subject=unsubscribe>

The parameters on the call on V5R1 are as follows:


This is the CL call.  To do a SEPT call, it shouldn't be much more 
involved.

DCL        VAR(&SPLFILNAM) TYPE(*CHAR) LEN(10) 
DCL        VAR(&JOBQUL) TYPE(*CHAR) LEN(26) 
DCL        VAR(&SPLNBR3) TYPE(*CHAR) LEN(4)             (this is a binary 
value it used to be 2 binary before V5R1)

 CALL       PGM(QSPDSPFM) PARM(&SPLFILNAM &JOBQUL 
              &SPLNBR3)

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QSPDSPFM parameters , Beppe Costagliola

This mailing list archive is Copyright 1997-2025 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.