First lets give an overview of the system situation here (all SAG products are on the latest version):
- PAC runs on mainframe
- NDV runs on mainframe
- Natural environment on mainframe
- NaturalONE runs on Windows PCs
- SVN is on a Linux machine
Inside of NaturalONE if you create a new Natural object, it is possible to have a different file name as the object name is.
The file name can have more than the 8 characters length limit and only must comply to the workspace filesystem rules (e.g. in NTFS you can include blanks and can not include &, etc.). The file name could even have no name of the Natural object in it!
Inside of the header section of the Natural Object the real object name is being kept inside the variable NatName.
Also NaturalONE does support library folders, so to get a more organized view onto your source modules. Please see in the N1 documentation for this.
Instead of directly connecting to the Natural environment on mainframe via the NDV, we are using SVN to store the sources. The Natural environment on mainframe is only being used to manually save and stow Natural objects during the development phase for testing only.
Now then, as soon the local development is done, you move the sources up to the next stage.
In this case, the sources are included as EXTERNAL source from the SVN into the PAC with status development.
AND here we arrived at my questions to you:
- Anyone knows, if the REQUEST DOCUMENT of PAC has a URL length limit and what it is?
- Also will PAC recognize the header of the Natural object and use the variable NatName to receive the real Natural Object Name instead of the filename (which is not suitable for mainframe)?
The documentation on REQUEST DOCUMENT only states that URL is of type A DYNAMIC. Those can get theoretically very large, and I am not sure, PAC can really work with the full specified length of 1GB. Well for URLs there seems to be a limit of 2000 characters. Is PAC going to work with that?