Ansicht
Dokumentation
03156 - Tagging of IFS-files (especially SAP profiles) has to be correct!
General Material Data BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Tagging of IFS-files (especially SAP profiles) has to be correct!
Hi Craig,you were on the right track!
I didn't fix the problem, so that you can do it on your own and know how to
proceed the next time. I posted it to the group as well because it sounds to
me interesting for more people around.
The profiles are mostly or all in ASCII (819). But at least the
default-profile has a contents of EBCDIC. As the SAP-system opens these
files as text-files the OS converts from ASCII to EBCDIC and generates only
rubbish! I suspect that you copied/moved the profiles with the NT-Explorer
and an AS/400 NetServer-Share. This is very dangerous, but possible when you
know what to do. When this share doesn't do any conversion at all, it has to
fail, because you read the files in the original system (there are probably
EBCDIC there) as EBCDIC unconverted to your PC and then put them back to the
next AS/400. Then the AS/400 "thinks" it should be ASCII and tags it like
this. Then this problem might have occured.
When you now have a look with EDTF or DSPF it shows you everything correct,
because these commands "look into the contents" and show it "useful", so
that when ASCII-characters are found, it shows the text as ASCII and for
EBCDIC vice versa. This behaviour is very, very crazy when you are hunting
for problems. Then sometimes (when the file is smaller then 1 page) it gives
you the warning that the CCSID were not correct. But when the file is longer
this warning is scrolled down by the IBM-copyright!!!
So you don't see it when you don't scroll up in the bottom line.
You could check the file with DSPF and F10, when you now see EBCDIC codes it
is EBCDIC (A = $C1, 1=$F1), when you see ASCII hexcodes it is ASCII (A =
$41, 1=$31). This has to fit to the tagging which you can check with the
attributes via 12 => wrklnk and then option 8.
When it doesn't fit it is bad, otherwise it will work, even when the file
AND the tagging is ASCII.
When you still want to use the NetServer, you would have to reconfigure the
share on the AS/400. Currently it is either without converting or converting
only with special suffixes. As the SAP files don't have any suffixes there
are thought to be "binary" (like EXE, DOC or PPT). Then you would have to
change it to convert even "*" => everything. When you now read over this
share binary files as well, it is necessary that they are really correct
tagged, otherwise they get corrupted because OS/400 then converts them from
the files CCSID to the NT-CCSID of the NetServer. But when you have a look
there, it will work fine.
Hope this helped and it worked as well when you change your configuration
files.
Regards
Volker
> -----Original Message-----
> From: Craig_WelchZb... [mailto:Craig_WelchZb...]
> Sent: Freitag, 7. September 2001 00:21
> To: Gueldenpfennig, Volker
> Subject: RE: V4R5 Profile Parameters - won't start
>
>
>
> Hi Volker,
>
> I hope you don't mind, but we are doing the V4R5 upgrade this
> weekend on
> our PRD box and we recreated a possible problem in our SAN
> box. I'm baffled
> by this one. Here's the story.
>
> We took a copy of our PRD profile over to the sandbox(V4R5)
> and I had the
> same problem. It's almost like a defect in the file itself? I
> really don't
> see how that's possible.
>
> The SAN instance started when I brought the Instance profile
> over from PRD.
> and changed the parameters referring to instance.
> (Embedded image moved to file: pic02995.pcx)
>
> When I brought over the DEFAULT profile parameter the system would not
> start. We even stripped all unnecessary lines of the profile
> and it still
> wouldn't start. Here's all that's left:
>
> (Embedded image moved to file: pic11942.pcx)
>
>
>
> I will gladly create an OSS message for you if you need it,
> otherwise if
> you wish to look at our system I have opened the connections
> and have the
> following user accounts for you on the AS/400.
>
> Craig Welch
> Brady Corporation
>
> SID SAN
> Sys no 88
> host GHOSA001
>
> OFR ID SANOFR
> OFR Passwd PGA520
>
> QSEC ID OSSSUPPORT
> QSEC Passwd OSSSUPPORT
>
> Here's a list of the files in the profile directory if you
> get a chance to
> look into it:
>
> Currently on SAN ->
>
> (Embedded image moved to file: pic04827.pcx) - is the PRD
> default with all
> comment lines (#'s) removed to match original SAN Default
> (currently being
> used by SAN)
>
> (Embedded image moved to file: pic32391.pcx) - is the PRD
> default adjusted
> for SAN.
> The system came up using this profile before using the
> PRD Default in
> item 1.
>
> (Embedded image moved to file: pic14604.pcx) - original SAN default
> replaced by
> item 2 above
>
> (Embedded image moved to file: pic03902.pcx) - original PRD
> default used to
> create
> item 1 above
>
> (Embedded image moved to file: pic00153.pcx) - original SAN default.
>
>
>
>
>
>
>
>
> "Gueldenpfennig,
>
> Volker" To:
> "'Craig_WelchZb...'"
> <volker.gueldenpfenni
> <Craig_WelchZb...>
> gZs...> cc:
>
> Subject:
> RE: V4R5 Profile Parameters
> 09/03/2001 09:17 AM
>
>
>
>
>
>
>
>
>
> Hi Craig,
>
> then we'll see what this result will be.
>
> Regards
>
> Volker
>
> > -----Original Message-----
> > From: Craig_WelchZb... [mailto:Craig_WelchZb...]
> > Sent: Montag, 3. September 2001 14:39
> > To: Gueldenpfennig, Volker
> > Subject: RE: V4R5 Profile Parameters
> >
> >
> >
> > Hi Volker,
> >
> > I didn't think there were any profile parameters that should
> > have a lower
> > limit so I was real surprised when two of my 3 systems on the
> > same host
> > would not start and stay up (work processes died). As soon as
> > I copied the
> > profile from the one that would start and changed the
> > instance info, the
> > system started right up. The instances with problems had been
> > running for a
> > year or more before the upgrade.
> >
> > I'm kinda spooked since our PRD DB and APP servers get
> > upgraded this coming
> > Friday. I will be trying to duplicate the problem on our
> > sandbox system
> > this week.
> >
> >
> > Craig.
> >
> >
> >
> >
> >
> >
> > "Gueldenpfennig,
> >
> > Volker" To:
> > "'craig_welchZb...'"
> > <volker.gueldenpfenni
> > <craig_welchZb...>
> > gZs...> cc:
> > "Sap400 (E-mail)" <sap400Zm...>
> > Subject:
> > RE: V4R5 Profile
> > 09/03/2001 01:00 AM Parameters
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Craig,
> >
> > there are definetely no real "profile-parameters" that
> prevent SAP to
> > start.
> > But you should use the latest kernel-patch (that is V4R5 compliant).
> >
> > Please have a look to the note 428855. This shows a lot
> > advised parameter
> > settings for your AS/400. But none of them should prevent you
> > from starting
> > your system - just a question of performance.
> >
> > Regards
> >
> > Volker
> >
> >
> >
> >
>
>
>
Durban Tours - Südafrika Safari
ABAP Short Reference SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 10160 Date: 20240416 Time: 101310 sap01-206 ( 4 ms )
