|
Apparently on V5R1 the form provides CCSID in place of Code Page: Display Attributes Object . . . . . . : /home/JDAMATO/libsa1.txt Type . . . . . . . . . . . . . . . . . : STMF Owner . . . . . . . . . . . . . . . . : JDAMA System object is on . . . . . . . . . : Local Auxiliary storage pool . . . . . . . . : 1 Object overflowed . . . . . . . . . : No Coded character set ID . . . . . . . . : 1252 Hidden file . . . . . . . . . . . . . : No PC system file . . . . . . . . . . . . : No Read only . . . . . . . . . . . . . . : No Need to archive (PC) . . . . . . . . . : Yes Need to archive (AS/400) . . . . . . . : Yes -----Original Message----- From: Scott Klement [mailto:klemscot@klements.com] Sent: Tuesday, April 16, 2002 11:44 PM To: 'midrange-l@midrange.com' Subject: RE: Determine IFS file type On Tue, 16 Apr 2002, Jim Damato wrote: > > When you look at the file attributes using WRKLNK you see the CCSID which > isn't, strictly speaking, the code page, is it? Hmmm... I don't know. You'd think that it'd be a CCSID, as you say -- at least that makes more sense to my tiny little mind. :) But my screen for WRKLNK says "Code Page", as does the docs for the stat() API, so I assumed that it was a code page. I'm at V4R5, and this is what it looks like: Display Attributes Object . . . . . . : /HOME/KLEMSCOT/test1.sgml Type . . . . . . . . . . . . . . . . . : STMF Owner . . . . . . . . . . . . . . . . : KLEMSCOT System object is on . . . . . . . . . : Local Auxiliary storage pool . . . . . . . . : 1 Object overflowed . . . . . . . . . : No Code page . . . . . . . . . . . . . . : 819 Hidden file . . . . . . . . . . . . . : No PC system file . . . . . . . . . . . . : No Read only . . . . . . . . . . . . . . : No Need to archive (PC) . . . . . . . . . : Yes Need to archive (AS/400) . . . . . . . : No
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.