From Terminal in namespace %SYS you can run

  • DO ^JOBEXAM
  • select your job by list of PID
  •  Job# NSpace  Routine        Commands   Globals State PID      Current device
       23 USER    shell               425        64 READ  17060    |TRM|:|17060
    Namespace:          USER                     SessionID:
    Routine:            shell
    Open Devices:       |TRM|:|17060*
    Mem Lim/Peak/Curr:  256M/154K/116K           In Trans:      No
    Priority:           8                        Info:
    User Name:          UnknownUser
    Roles/EscalatedRoles:%All/None
    OS User Name:       cemper                   EXE Name:
    Client Node Name:   TRM:                     IP Address:    127.0.0.1
    Location:                                    PrivGblBlks:   3
    Last reference:     ||RCC(5)
     
    Current line:
     
    Entry Process     X#   S# Flg Item Locked
    
    (V)ariable, (L)ocks, (S)tack, (P)rocess Private Globals, (Q)uit =>  P
  • and can see  PPG
    Process Private Global (?): RCC
    ^||RCC(1)=1
    ^||RCC(2)=2
    ^||RCC(3)=3
    ^||RCC(4)=4
    ^||RCC(5)=5
     
    Process Private Global (?):
     

Hi @Michael Davidovich !
you hit exactly what I addressed in in my recent article
  The bewitched line terminator

As long as you get (text-) files from your own OS the default is OK
BUT: if you work cross OS platforms - rather likely for CSP pages -
the approach of  
%CSP.BinaryStream is the best for import.

For output stream you have to decide based on the expected target OS.

My personal trigger to that subject was file transfer between
WIN as Docker host and a Container (Ubuntu) causing a lot of  confusion until detected.
 

Open Exchange applications:
Certifications & Credly badges:
Global Masters badges:
Followers:
Following: