|
I don't think you need the &squote literals. The command prompter uses them to indicate that the value is a character string, but I don't think they're necessary when passing the command in a variable. Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 -----Original Message----- From: R Allen [mailto:rallen@xxxxxxxxxxx] Sent: Tuesday, November 30, 2004 4:34 PM To: 'Midrange Systems Technical Discussion' Subject: QSH with variable vs hard coding Hello all! I have a CL program that executes the following QSH CMD('jar -cfM /JOHN/TESTZIP1.ZIP /JOHN/TESTZIP1.PDF') and it works fine. I changed the CL to remove the hard coded file names: DCL VAR(&PDFFILE) TYPE(*CHAR) LEN(50) VALUE('/JOHN/TESTZIP1.PDF') DCL VAR(&ZIPFILE) TYPE(*CHAR) LEN(50) VALUE('/JOHN/TESTZIP1.ZIP') DCL VAR(&CMD) TYPE(*CHAR) LEN(256) DCL VAR(&SQUOTE) TYPE(*CHAR) LEN(1) value('''') CHGVAR VAR(&CMD) VALUE(&SQUOTE *TCAT 'jar -cfM' *BCAT &ZIPFILE *BCAT &PDFFILE *TCAT &SQUOTE) QSH CMD(&CMD) ENDPGM In debug the variable &CMD shows a value of 'jar -cfM /JOHN/TESTZIP1.ZIP /JOHN/TESTZIP1.PDF' (includes the singles quotes) But this method fails with message qsh: 001-0014 Command jar -cfM /JOHN/TESTZIP1.ZIP /JOHN/TESTZIP1.PDF not found. These test are being run interactively, I can't seem to see a difference between the two. Anyone have any suggestions? John -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.