Re: Odd error with .profile in QP2TERM

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Hi Pete,

I think the original problem was that you created your .profile file in 
EBCDIC.  That would work fine in QShell, but not in QP2TERM, since PASE 
is Unix, it doesn't understand EBCDIC.

Now that you've re-made the file with vi, the data will definitely be 
encoded in ASCII -- but the system would put a default CCSID on it, so 
the CCSID may be ending up as EBCDIC.  In that case, it'd work fine in 
PASE (which ignores CCSIDs in the file system, since AIX doesn't have 
them there) but would not work in QShell, since QShell relies on the 
CCSID of the object.

However, the fix for this 2nd problem is easy, just do:
CHGATR OBJ('/home/whatever/.profile') ATR(*CCSID) VALUE(819)

That will tell the system that the data is ASCII (which is what vi 
would've put in there) so it should now understand the file from anywhere.


On 10/29/2014 3:55 PM, Pete Helgren wrote:
> Thanks Bryan...I checked and that was the option that was already selected.
>
> This is some kind of weird CCSID mismatch issue.  I was also having
> issues logging in using SSH because all I got was garbage like so:
>
> -bsh: ñK÷Kñöa^M%ÑÁåÁmÈÖÔÅ~aØÖ
> ⨢aØÉÂÔa×
>            Ä£aÑ¥åÔa
>                    öòöaóò£^M%
> §£@×ÁãÈ@ÑÁåÁmÈÖÔÅ^M%: not found
> -bsh: {Zaa¢^M%×ÁãÈ~a¤¢azKzaØÖ
> ⨢a¤¢aza¤¢aa¤¨: not found
>
> When I deleted the .profile file, all was well.  So I recreated it using
> EDTF and all I got was the garbage again in SSH.  So, I deleted the
> .profile file again and then logged in using SSH and used vi to create
> the .profile file.  THAT .profile worked like a charm in SSH and QP2TERM
> but when I use QSHELL now I get a similar message there:
>
> qsh: 001-0049 Syntax error on line 1: token end of file not expected,
> expecting token "`".
>
> When I use EDTF to edit the .profile file created with vi, I now get an
> error:
>
>   Message ID . . . . . . : CPDB609
>   Date sent  . . . . . . :   10/28/14      Time sent  . . . . . . :
> 09:14:30
>
>   Message . . . . :   File CCSID not valid.
>
>   Cause . . . . . :   The file Coded Character Set Identifier (CCSID)
> was 00037,
>     but the data in the file looks like ASCII. A CCSID of 00819 is being
> used.
>   Recovery  . . . :   If another CCSID is needed, use F15 to change to the
>     desired CCSID.
>
> And yes, the system/job CCSID is 37 and the CCSID on the .profile is 00819
>
> So it seems I can satisfy either SSH OR QSHELL but not both.  I am sure
> that it is a CCSID issue but I am not quite sure how to fix it.  Right
> now I am sticking with SSH and QP2TERM but I'd love to know why I can't
> get the .profile CCSID set so both environments are happy with it.
>
> Pete
>
> On 10/29/2014 1:35 PM, Bryan Dietz wrote:
> > Maybe you need to make sure there are no CRLF in the file.
> >
> > If using EDTF press F-15 and choose
> > option 5 (at top)
> >
> > and
> >
> > 5. Stream file EOL option . . . .     *LF
> >
> >
> > bryan
> >
> >
> >
> > Pete Helgren wrote on 10/25/2014 8:14 AM:
> > > When I start QP2Term I get this error:
> > >
> > > .profile: 0403-057 Syntax error: ``' is not matched.
> > >
> > > Yet when I check my profile: EDTF ".profile"  I see this:
> > >
> > > #!/bin/sh
> > > PATH=/usr/bin:.:/QOpenSys/usr/bin:/usr/local/jruby-1.7.16/bin
> > > JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk626/32bit
> > > export PATH JAVA_HOME
> > >
> > > I don't see any '  (single or double quotes).. So what profile is it
> > > complaining about?