Hi everyone,
We have a productive system i server and a backup system i server.
On our productive server, we have the following IFS www directories and CCSIDs:
1. /www ==> ccsid 500
2. /www/ajsp ==> ccsid 37
3. /www/apachedft ==> ccsid 500
4. /www/iwadft ==> ccsid 500
5. /www/profoundui ==> ccsid 500
On our backup server, we have the following IFS www directories and CCSIDs:
6. /www ==> ccsid 37
7. /www/ajsp ==> ccsid 37
8. /www/apachedft ==> ccsid 37
9. /www/iwadft ==> ccsid 37
10. /www/profoundui ==> ccsid 500
To make sure that our sync process from the productive server to the backup server runs properly, we have to change some of the CCSIDs above from 37 to 500.
Our question: Can we change the CCSIDs of the IFS directories 6., 8. and 9. from 37 to 500 (including sub-folders) or is it problematic ? If it is problematic, is there another way to solve this issue ?
Thank you very much for your answer in advance and feel free to ask if you need more Information.
Christoph
IFS www directory - Question about CCSID
-
- Profound User
- Posts: 53
- Joined: Tue Jan 27, 2015 8:13 am
- First Name: Christoph
- Last Name: Seitz
- Company Name: Waser + Co. AG
- Phone: +41 44 94 74 341
- Address 1: Erlenwiesenstrasse 2
- City: Volketswil
- State / Province: Outside Canada/USA
- Zip / Postal Code: 8604
- Country: Switzerland
- Contact:
-
- Experienced User
- Posts: 2711
- Joined: Wed Aug 01, 2012 8:58 am
- First Name: Scott
- Last Name: Klement
- Company Name: Profound Logic
- City: Milwaukee
- State / Province: Wisconsin
Re: IFS www directory - Question about CCSID
Are you referring to the CCSID of the directory itself, or the objects inside that directory?
If you are referring to the directories themselves, it doesn't matter what the CCSID is since the names you've shown have the same code points in both 37 and 500. (They are just basic lowercase letters, which are the same in almost all CCSIDs -- the only exceptions I'm aware of are environments that don't support lowercase, such as some Japanese CCSIDs)
If you are referring to the objects inside those directories, then I can only help you with the Profound-logic supplied stuff. I am not familiar with the "ajsp", "apachedft" or "iwadft" instances or what they contain. Likewise, I don't know about any content you may have placed in the profoundui instance yourself, such as custom javascript, css or html files. I only know about the objects that come with our product.
The objects in our product should all be CCSID 819 or 1208. None of the IFS stuff is in EBCDIC, so should not be 37 or 500 on any of your boxes. (This is why I think you probably are only referring to the directory itself, and not it's contents.)
If you are referring to the directories themselves, it doesn't matter what the CCSID is since the names you've shown have the same code points in both 37 and 500. (They are just basic lowercase letters, which are the same in almost all CCSIDs -- the only exceptions I'm aware of are environments that don't support lowercase, such as some Japanese CCSIDs)
If you are referring to the objects inside those directories, then I can only help you with the Profound-logic supplied stuff. I am not familiar with the "ajsp", "apachedft" or "iwadft" instances or what they contain. Likewise, I don't know about any content you may have placed in the profoundui instance yourself, such as custom javascript, css or html files. I only know about the objects that come with our product.
The objects in our product should all be CCSID 819 or 1208. None of the IFS stuff is in EBCDIC, so should not be 37 or 500 on any of your boxes. (This is why I think you probably are only referring to the directory itself, and not it's contents.)
Who is online
Users browsing this forum: No registered users and 3 guests