Skip to main content
4everJang
4everJang
Legend
July 28, 2014
Answered

Syntax of a FrameMaker "lck" file

  • July 28, 2014
  • 2 replies
  • 972 views

Does anyone know what the entries in the FrameMaker "lck" file represent ? I can guess at some of them, but if there is some kind of reference info somewhere, that would be useful.

Thanks

Jang

    This topic has been closed for replies.
    Correct answer Bob_Niland

    On either Unix (FM7) or Win7 (FM9), the string looks like:

    username/Real Name/sysname/Mon Jul 28 07:43:27 2014/1406551407/1/

    username/

    Login name of user holding lock

    /Real Name/

    Full name of that user

    /sysname/

    System (PC, workstation, or VM instance I suppose) name

    /Mon Jul 28 07:43:27 2014/

    Time of most recent Write (apparently not time of Open)

    /1406551407/

    Might be same timestamp, as Unix Epoch (seconds since 00:00:00 1970-01-01 UTC).

    Might also be some other time, such as Open. The Solaris system I'm using lacks a manpage for the various date and clock commands, and isn't responding to standard options, so I wasn't able to decode it. The readable date and the 14.... are real instance. If they match, it's Write date. If the 14... stamp is earlier by minutes, it's Open.

    /1/

    Beats me, but was "1" on both systems.

    2 replies

    Bob_Niland
    Community Expert
    Bob_NilandCommunity ExpertCorrect answer
    Community Expert
    July 28, 2014

    On either Unix (FM7) or Win7 (FM9), the string looks like:

    username/Real Name/sysname/Mon Jul 28 07:43:27 2014/1406551407/1/

    username/

    Login name of user holding lock

    /Real Name/

    Full name of that user

    /sysname/

    System (PC, workstation, or VM instance I suppose) name

    /Mon Jul 28 07:43:27 2014/

    Time of most recent Write (apparently not time of Open)

    /1406551407/

    Might be same timestamp, as Unix Epoch (seconds since 00:00:00 1970-01-01 UTC).

    Might also be some other time, such as Open. The Solaris system I'm using lacks a manpage for the various date and clock commands, and isn't responding to standard options, so I wasn't able to decode it. The readable date and the 14.... are real instance. If they match, it's Write date. If the 14... stamp is earlier by minutes, it's Open.

    /1/

    Beats me, but was "1" on both systems.

    4everJang
    4everJangAuthor
    Legend
    July 28, 2014

    Thanks,

    I was assuming this, but as my user and real name (on my 1-person company computer) is the same, I was unsure about which one was which. Could have tested it of course but I was hoping this forum would be quicker.

    Jang

    W
    Community Expert
    Winfried RengCommunity Expert
    Community Expert
    July 28, 2014

    Hi Jang,

    Only additional information. The date seems to be of the format/language of your system.

    I have FrameMaker English on a German Windows system and the date is in German and in the German format.

    Best regards

    Winfried

    A
    Art_Campbell1
    Inspiring
    July 28, 2014

    OK, I'm curious, and I'm not going to be helpful because I have no idea of

    the syntax.

    But I have to ask... it's a network locking file, with one setting -- it's

    only present if the file is open on someone's desktop.

    What can you do with either the file or the syntax?

    Art Campbell

    art.campbell@gmail.com

    "... In my opinion, there's nothing in this world beats a '52 Vincent and

    a redheaded girl." -- Richard Thompson

    No disclaimers apply.

    DoD 358

    I support www.TheGrotonLine.com, hyperlocal news for Groton MA.

    4everJang
    4everJangAuthor
    Legend
    July 28, 2014

    Hello Art,

    At normal FM termination, the file is closed and the lock file is deleted. But when a program or script has crashed, that does not happen. The lock file is still there even though the file is not open in anyone's application. When you try to open the file, there is a dialog showing that the file is in use - it lists the user who supposedly has the file open in their FM application. You can then reset the lock and continue. My script opens files in the background (invisible) and needs to reset the lock when appropriate. So I will have to check the info from the lock file against the user who is currently logged in (and possibly also the computer on which the application is running). I don't want to remove the lock file from a network drive when someone else is currently working on it. But I also do not want to keep my script from working when an obsolete lock file still exists as the remains of an earlier crash or bug in the FM application (which also occurs every once in a while).


    I posted it here instead of in the Scripting forum, as the syntax of the file is not specific to scripting or programming.


    Kind regards


    Jang


    A
    Art_Campbell1
    Inspiring
    July 28, 2014

    Thank, Jang! Curiosity satisfied.

    Cheers,

    Art

    Art Campbell

    art.campbell@gmail.com

    "... In my opinion, there's nothing in this world beats a '52 Vincent and

    a redheaded girl." -- Richard Thompson

    No disclaimers apply.

    DoD 358

    I support www.TheGrotonLine.com, hyperlocal news for Groton MA.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices