RE: Clearing a physical file

PSDS has been around since the beginning of time - or 1980, whichever comes 
first. It's populated by the RPG at various times. More info can be had in the 
ILE RPG Reference, as well as a few items in the ILE RPG Programming Guide. 
There are also INFDS' you can set for files, which can get you lots of info.
-------------- Original message -------------- 
From: Michael_Schutte@xxxxxxxxxxxx 

> That's certainly true, however, the uses I needed it for I have had the 
> need to look at the information. All I cared about is if the command 
> executed or not. Like you, I was unaware of the psds. Is that something 
> that needs to be defined? or is available to use similar to a BIF? 
> 
> Michael Schutte 
> Work 614-492-7419 
> email michael_schutte@xxxxxxxxxxxx 
> 
> 
> 
> rob@xxxxxxxxx 
> Sent by: 
> midrange-l-bounce To 
> s@xxxxxxxxxxxx Midrange Systems Technical 
> Discussion 
> 
> 03/31/2006 09:03 cc 
> AM 
> Subject 
> RE: Clearing a physical file 
> Please respond to 
> Midrange Systems 
> Technical 
> Discussion 
> > nge.com> 
> 
> 
> 
> 
> 
> 
> Michael, 
> 
> I used to really like system also. I do have it buried in a lot of 
> programs. However, Barb talked me back to using QCMDEXC. When you use 
> QCMDEXC you can look at the psds and get more feedback if the command 
> fails. Like "Why did it fail"? Granted, if you really want unlimited 
> information, you'd use QCAPCMD. But for most applications, QCMDEXC 
> suffices. 
> 
> Rob Berendt 
> -- 
> Group Dekko Services, LLC 
> Dept 01.073 
> PO Box 2000 
> Dock 108 
> 6928N 400E 
> Kendallville, IN 46755 
> http://www.dekko.com 
> 
> 
> 
> 
> 
> Michael_Schutte@xxxxxxxxxxxx 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx 
> 03/31/2006 08:45 AM 
> Please respond to 
> Midrange Systems Technical Discussion 
> 
> 
> To 
> Midrange Systems Technical Discussion 
> cc 
> 
> Subject 
> RE: Clearing a physical file 
> 
> 
> 
> 
> 
> 
> I have an easier one. It requires binding a directory. Here's the code. 
> 
> H Bnddir('QC2LE') 
> 
> * Allows you to execute a CL command from RPG. 
> D DoCmd PR 10i 0 ExtProc('system') 
> D CmdString * Value 
> D Options(*String) 
> 
> D NullString C -1 
> D Success C 0 
> 
> /Free 
> If DoCmd('CLRPFM MYFILE') <> SUCCESS; 
> ... DO SOMETHING 
> EndIf; 
> ... Do Something 
> *InLR = *On; 
> Return; 
> /End-Free 
> 
> 
> 
> Michael Schutte 
> Work 614-492-7419 
> email michael_schutte@xxxxxxxxxxxx 
> 
> 
> 
> "Lindbom, Joakim" 
> > apgemini.com> To 
> 
> Sent by: "Midrange Systems Technical 
> midrange-l-bounce Discussion" 
> s@xxxxxxxxxxxx 
> cc 
> 
> 
> 03/31/2006 08:10 Subject 
> 
> AM RE: Clearing a physical file 
> 
> 
> Please respond to 
> Midrange Systems 
> Technical 
> Discussion 
> > nge.com> 
> 
> 
> 
> 
> 
> 
> 
> Just call QCMDEXC with the command as a parameter, something like: 
> 
> D Cmd PR ExtPgm('QCMDEXC') 
> D Command 200A const 
> D Length 15P 5 const 
> 
> C callp Cmd('CLRPFM FILE(' %trim(filename) + ')': 
> 200) 
> 
> 
> /Joakim 
> 
> ________________________________________________________________________ 
> _____ 
> Joakim Lindbom 
> Capgemini Sweden 
> 
> There are 10 kinds of people; those who can read binary and those who 
> can not. 
> 
> -----Original Message----- 
> .... 
> Is there coding to clear a physical file within a RPGLE program without 
> calling a CL program to clear it? 
> .... 
> 
> This message contains information that may be privileged or confidential 
> and is the property of the Capgemini Group. It is intended only for the 
> person to whom it is addressed. If you are not the intended recipient, you 
> are not authorized to read, print, retain, copy, disseminate, distribute, 
> or use this message or any part thereof. If you receive this message in 
> error, please notify the sender immediately and delete all copies of this 
> message. 
> 
> 
> -- 
> 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. 
> 
> 
> 
> -- 
> 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. 
> 
> 
> -- 
> 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. 
> 
> 
> 
> -- 
> 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. 
>