cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X

Syntax for CREO *.PSF and *.PRO file

ZWei
6-Contributor

Syntax for CREO *.PSF and *.PRO file

Is there any documentation on the syntax for *.PSF and *.PRO file (eg: syntax for comment out line, etc) ? 

 

For PSF file, i always  under the assumption that // is used to comment out a line.

However, i notice that if i change the first line // PTC - PSF file: parametric to something like // PTC - PSF file: parametric2, the PSF file will no longer work. 

 

 

ZWei_0-1685582653154.png

ZWei_1-1685582704885.png

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
MartinHanak
24-Ruby II
(To:ZWei)

Hi,

 

config.pro

  • comment line starts with ! character (exclamation mark)
  • line which sets something consists of 2 words ... option_name  option value

 

parametric.psf

  • syntax description does not exist
  • you must not modify lines created by installer ... there are a few exceptions
  • when editing psf file in Notepad, you can
    • modify description
      • DESC=licensedescription
    • modify path to license
      • ENV=PTC_D_LICENSE_FILE-=7788@licenseservername
    • modify license_name
      • ENV=CREOPMA_FEATURE_NAME=licensename
    • add lines at the end of the file
      • ENV=variablename=variablevalue
      • RUN=path_to_command

If you need some other information, please provide detailed description of your "goal".


Martin Hanák

View solution in original post

3 REPLIES 3
MartinHanak
24-Ruby II
(To:ZWei)

Hi,

 

config.pro

  • comment line starts with ! character (exclamation mark)
  • line which sets something consists of 2 words ... option_name  option value

 

parametric.psf

  • syntax description does not exist
  • you must not modify lines created by installer ... there are a few exceptions
  • when editing psf file in Notepad, you can
    • modify description
      • DESC=licensedescription
    • modify path to license
      • ENV=PTC_D_LICENSE_FILE-=7788@licenseservername
    • modify license_name
      • ENV=CREOPMA_FEATURE_NAME=licensename
    • add lines at the end of the file
      • ENV=variablename=variablevalue
      • RUN=path_to_command

If you need some other information, please provide detailed description of your "goal".


Martin Hanák
ZWei
6-Contributor
(To:MartinHanak)

Basically i would just like to include some comment in the PSF file and PRO file (eg: Revision, comment on changes, etc)   

 

From first glance, the default PSF file seems to use // to comment out the line but it seems like it does not really work as comment out since changing the first line of comment [// PTC - PSF file: parametric] will break the file 

ZWei_1-1685663726391.png

 

 

MartinHanak
24-Ruby II
(To:ZWei)


@ZWei wrote:

Basically i would just like to include some comment in the PSF file and PRO file (eg: Revision, comment on changes, etc)   

 

From first glance, the default PSF file seems to use // to comment out the line but it seems like it does not really work as comment out since changing the first line of comment [// PTC - PSF file: parametric] will break the file 

ZWei_1-1685663726391.png

 

 


Hi,

so you provided information. I am missing your questions.

 

config.pro

  • comment line starts with ! character (exclamation mark)
  • you can add a comment line anywhere in the file

 

parametric.psf

  • you can add lines at the end of the file, only
  • add new lines below following lines
// USER - PSF
// Add User specific environment or run applications below here
  • comment line starts with // (double slash)

 


Martin Hanák
Top Tags